epistex-dev/poteto-kit / templates/skills/verify-app
verify-app
UnverifiedRun the real {{APP_NAME}} the way users reach it, drive it, and capture evidence (screenshot, console errors, performance trace, heap snapshot). Use to reproduce a bug report, verify a fix or feature before claiming it works, or measure performance. Never report "should work" without evidence from a real run.
Security report
UnverifiedStatic analysis of one exact version. It reduces risk and shows evidence; it does not certify that a skill is safe.
- Commit
7d0e29008d567d6f2516771a1cf6e980dab80958- Content hash
d48b73682f205a4621e19fae7919c1fb2dc8b53075a8bbb82ee5e921f658a352- Scanned
- 2026-11-18
- Scanner version
- skillxone-scan-1.0.0
- Policy version
- 0.1-draft
- Decision
- 10 open medium findings to review.
- Verification expires
- Not applicable
Findings (10 medium)
An HTML comment contains instructions. Comments are hidden when the file is rendered, so a reader would not see them, but an agent reading the raw file would.
1. Keep this file next to SKILL.md. It is the spec of the verify CLI: read it before you build or change the CLI, and change it in the same commit as the CLI's behavior. An agent that only runs verifications does not need it: what it must …Suggested fix: Move instructions into visible text, or remove the comment.
An HTML comment contains instructions. Comments are hidden when the file is rendered, so a reader would not see them, but an agent reading the raw file would.
1. Keep this file only if agents run the control skill in cloud agent VMs or CI-like sandboxes. Fill the {{PLACEHOLDERS}} with your real commands and locations; delete the sections your app type does not need.Suggested fix: Move instructions into visible text, or remove the comment.
An HTML comment contains instructions. Comments are hidden when the file is rendered, so a reader would not see them, but an agent reading the raw file would.
2. It is a contract for the VM image and the CLI, not a script: build the pieces it names (a seed command, an artifact upload step) once, test them, then let agents rely on them.Suggested fix: Move instructions into visible text, or remove the comment.
An HTML comment contains instructions. Comments are hidden when the file is rendered, so a reader would not see them, but an agent reading the raw file would.
1. Keep this file only if someone besides the agent has to read the evidence (a lead, a client, an auditor) in a form other than Markdown. Otherwise delete it.Suggested fix: Move instructions into visible text, or remove the comment.
An HTML comment contains instructions. Comments are hidden when the file is rendered, so a reader would not see them, but an agent reading the raw file would.
2. Write for an agent that has never seen the app. Describe use, not implementation. Every step is something a user does; every selector is something you checked in a running app.Suggested fix: Move instructions into visible text, or remove the comment.
An HTML comment contains instructions. Comments are hidden when the file is rendered, so a reader would not see them, but an agent reading the raw file would.
4. A full sweep (README.md) finishes with these flows. A change touching two or more features should run the relevant flows here as well as each feature file.Suggested fix: Move instructions into visible text, or remove the comment.
An HTML comment contains instructions. Comments are hidden when the file is rendered, so a reader would not see them, but an agent reading the raw file would.
3. Or let the agent draft the first version with skills/create-verification/SKILL.md, then review it yourself: you know what users really do.Suggested fix: Move instructions into visible text, or remove the comment.
An HTML comment contains instructions. Comments are hidden when the file is rendered, so a reader would not see them, but an agent reading the raw file would.
1. Keep this file only if several agents (or an agent and a human) may run the app at the same time on one machine. Fill the {{PLACEHOLDERS}} with your real commands; delete anything your stack does not need.Suggested fix: Move instructions into visible text, or remove the comment.
An HTML comment contains instructions. Comments are hidden when the file is rendered, so a reader would not see them, but an agent reading the raw file would.
3. Install it as .agents/skills/verify-app/ (the canonical location; see the install table in templates/README.md for Claude Code, Cursor and Codex). Keep the folder name equal to `name` above.Suggested fix: Move instructions into visible text, or remove the comment.
An HTML comment contains instructions. Comments are hidden when the file is rendered, so a reader would not see them, but an agent reading the raw file would.
4. `disable-model-invocation: false` is a literal so the frontmatter stays valid YAML, and it lets the agent load the skill when the description matches. Set it to `true` only if you want an explicit /verify-app. When to choose which, and …Suggested fix: Move instructions into visible text, or remove the comment.
Checks run
- prompt-injection
- dangerous-commands
- credentials
- network
- file-access
- integrity
Checks skipped
- dependencies: No dependency manifest in the skill directory.
- gitleaks: gitleaks is not installed on this host.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |