agentleFS
mag123cmag123c/toktrack/.claude/skills/wrap/SKILL.md

wrap

Skill196 starsChanged 13 days agoMITView on GitHub

Session end - document updates, commit

46 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use start, update 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.
  • AnthropicSkill

    start

    Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.

    Also in 5 projects that use this

  • AnthropicSkill

    update

    Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.

    Also in 3 projects that use this

  • LangChainSkill

    remember

    Review the current conversation and capture valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says: (1) remember this, (2) save what we learned, (3) update memory, (4) capture learnings.

    Also in 3 projects that use this

  • termdockSkill

    recall

    Retrieves cross-session memories about past decisions, lessons, and patterns. Use when user asks about prior work, past decisions, or mentions a feature. Triggers include check memory, what did we decide, how did we solve.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    build

    Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.

    Also in 3 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 3 projects that use this

  • +1 more from anthropics

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 40 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:

    Execute: Run selected items

    line 42

“Common” is measured: kept by at least 6 in 10 of the 40 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

Wrap

Flow

Git Status → Doc Check → User Selection → Execute → Complete

Execution

  1. Git Status
    git status --short
    git diff --stat HEAD~3
  2. Doc Check Checklist (MUST)

    ChangeTargetRequired
    trait/typearchitecture.mdon structural change
    conventionconventions.mdon new pattern
    Decisions.dev/DECISIONS.mdon new feature/design

    DECISIONS.md entries (required check):

    • New feature implemented → record decision rationale, alternatives, reasons
    • Divergence between PLAN and actual implementation → add **Implementation Note**
    • New pattern/convention → also update conventions.md
  3. Plan Reconciliation (MUST)

    Reconcile the PLAN's provenance tags/gates ([unverified-gate]/[agent-inferred]/Phase 0) one-by-one — close (confirmed/falsified/changed) or explicitly delegate (delegated). No silent TODOs. Unsettled gates = wrap incomplete.

    Detailed procedure·delegated block·escalation criteria (WRAP=detail/DECISIONS=why/CLAUDE.md=critical·recurring) → references/reconciliation.md

  4. User Selection: AskUserQuestion
  5. Execute: Run selected items

DSL Rules (ai-context)

  • Table > prose
  • Codeblock > description
  • Core only, minimize lines

Commit

{type}({scope}): {summary}

Completion

wrap complete = skill chain finished Next task starts with new /clarify or /next

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.