agentic-walkthrough
From the author
Prove that a reported run caused its intended real effect. Walk the executor path from entry to effect, capture one observable per hop, and report a result a no-op could not produce.
Install
npx skills add sno-ai/sno-station-skills --skill agentic-walkthrough -a claude-code
Installs to .claude/skills/agentic-walkthrough/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 81
Security85
Provenance75
Maintenance100
Licence100
Adoption48
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- browser-walkthroughDasDigitaleMomentum/opencode-processing-skillsRun Playwright-MCP browser acceptance, agent-observed walkthroughs, or user-attended walkthroughs through the role routing appropriate to each mode, returning a compact evidence-referenced digest.Browser★ 61
- goal-driven-executionDevelopersGlobal/ai-agent-skillsTransforms imperative instructions into declarative goals with verifiable success criteria. Enables autonomous looping until verified completion.Other★ 216
- wake-traceamplifthq/openmeldUse when diagnosing a Wake that failed, stalled, or produced no visible reply — dispatch, setup handoff, or reply-path issues. Routes to the deterministic trace evidence path.Other★ 1.4K
- append-run-logOutlineDriven/outline-driven-developmentUse when a completed agent run must be recorded as durable, queryable evidence. Not for remote, credential, publish, deploy, or irreversible changes.DevOps★ 55
- playtesting-a-featureSummerEngine/summerBefore calling a gameplay feature done, run the game and walk through it. Static checks do not count.Other★ 89
- agentic-tddreticlehq/reticleTest-driven development for behaviour a unit test cannot reach, by writing the expectation against the running app before writing the code. Declare the consequence first, watch it fail, implement, watch it pass. Use when building a user-facing feature, when the user asks for TDD on UI or full-stack work, when a unit test cannot express the outcome that matters, or when you want a red-green loop that runs against the real app instead of mocks.Testing★ 1.3K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in