agentleFS
woodbearywoodbeary/later-dog/.agents/skills/create-verification-skill/SKILL.md

create-verification-skill

Skill2 starsChanged 29 days agoApache-2.0View on GitHub

Write a verification skill for a repository: how to start it in isolation, drive what a user really does, keep evidence that survives cleanup, and map its main features, proven by running it once.

93 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-pstack, principle-explain-the-number and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 31 projects that use this

  • shiwenbin1617Skill

    principle-explain-the-number

    Apply before you measure, and before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 35 projects that use this

  • shiwenbin1617Skill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 17 projects that use this

  • drafaelSkill

    in-your-own-words

    Restate the user's goals and the problem they are trying to solve to check understanding. Manual invocation only; use when the user explicitly invokes in-your-own-words or requests this understanding check. Do not solve the task or rewrite the assistant's last answer.

    Also in 32 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 22 projects that use this

  • instructureSkill

    ketchup

    Rebuild context after /clear by analyzing uncommitted changes across Canvas LMS and all plugin repositories

    Also in 28 projects that use this

  • +3 more from shiwenbin1617

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 80 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the harness that exists: If it is broken, fix it first in a draft PR.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 80 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create verification skill

Use when a repository gives agents no dependable way to show that a change works, or when asked for a verification skill. later.dog's own setup is the model: docs/verification/README.md with scripts/control-laterdog.ts, and the verify-laterdog skill with its feature map. Use the later.dog MCP server. Discover tools by the names below; client-specific prefixes may vary.

Procedure

  1. Find out how the app really runs, from its code and docs: how people reach it (screens, CLI, API), the start command and the signal that it is ready, any test harness or control CLI already there, stable handles (accessible names, routes, commands, test IDs), the side effects worth checking, and how to keep a run's data separate (temporary directory, fake provider, its own port).
  2. Use the harness that exists. If it is broken, fix it first in a draft PR; instructions written around a broken harness teach the wrong steps. If there is none, say so and propose the smallest script that would do. Never invent commands or selectors.
  3. Write verify-<app>/SKILL.md where the repository's agents look for skills: in a repository laid out like later.dog, the canonical folder and then its export command; otherwise .agents/skills/. Give it a name and a description, then:
    • Start: the exact command, isolated data and the ready signal.
    • Check: one read-only health check whose failure says what to do next.
    • Drive: commands and stable handles taken from the code, never screen coordinates.
    • Evidence: the action, the state it produced and any side effect, kept outside anything cleanup deletes.
    • Stop: end only what this run started, and leave the evidence.
  4. Map the features: features/README.md and one page per important feature, saying where a person meets it, how to drive it, what proves it worked and what that proof leaves open.
  5. Run it once, end to end, on one mapped feature: start, check, drive, keep evidence, stop, then confirm the evidence is still there. A skill nobody has run is not finished. Fake only services outside the repository and say which results came from a fake: fixture success does not qualify a live provider.
  6. Feed cloud verification. From the map, pick the CI checks and isolated commands that really exercise behaviour; they become the repository's recipe through configure_verification_recipe. That tool needs the admin connection, so a dog asks its person to enter the checks in Cloud jobs → Connect repository.
  7. Leave upkeep to the maintain-verification-skill skill.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.