AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Unfold

skill-railly-skills-unfold · by Railly

Understand, diagnose, change, or review an unfamiliar codebase through one evidence-backed mission. Use when learning architecture, tracing a feature, investigating a bug, implementing a real change with guided or agent execution, reviewing a diff or PR, or checking whether tests and the built artifact prove the intended behavior. Prefer over prose-only repository explanations and ungrounded debu…

↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-railly-skills-unfold

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-railly-skills-unfold)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● today

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Unfold? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Unfold

Turn one maintenance mission into a navigable mental model, an evidence-backed change, and proof proportional to the work. Reuse what has already been established instead of restarting the repository tour at every phase.

1. Establish the mission

Frame one concrete question or outcome:

> How does [operation or symptom] travel from [entry] to [outcome], and what evidence would prove the result?

Read existing .unfold/ artifacts before broad exploration. Compare their recorded commit with HEAD and reverify decisive anchors against current source.

Read [references/protocol.md](references/protocol.md) for the shared evidence and artifact contract.

2. Select the earliest incomplete mode

Choose one primary mode. Load only its reference.

| User state | Mode | Reference | |---|---|---| | Wants to understand a system or flow | Learn | [learn.md](references/learn.md) | | Has a symptom, failing behavior, or issue | Triage | [triage.md](references/triage.md) | | Has a known change to implement | Change | [change.md](references/change.md) | | Has a diff, patch, test, or PR to assess | Review | [review.md](references/review.md) |

Enter directly at the earliest unfinished state. Do not repeat completed work. A verified Triage Change Surface can enter Change; a finished patch can enter Review; Learn can support any mode when the user lacks a load-bearing part of the mental model.

3. Preserve one evidence chain

Carry the same mission, commit, claims, anchors, unknowns, and artifacts across mode transitions. Keep distinctions that change the causal story: setup/runtime/teardown, automatic/manual, caller/owner, persisted/cached, current/proposed, and component/file/function/contract.

When a visual materially clarifies the mission, read [references/visuals.md](references/visuals.md) and render the smallest useful diagram. When durable output is authorized, follow [references/artifacts.md](references/artifacts.md).

4. Respect the collaboration policy

Learn is reconstructive by default. Triage remains read-only until the user requests a patch. Change explicitly selects guided, execute, or execute-with-approval. Review may alter tests only when the user authorized review changes.

Never let a mode transition silently broaden write, commit, push, tracker, or release authority.

Close the mission

Report the result, decisive evidence, remaining unknowns, and the next unfinished mode. The outcome is complete only when the claim is understandable and its proof is retrievable.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills