Agent skill

Loopany Capture

by superdesigndev in superdesigndev/loopany

Decides, once a task is finished, whether the outcome deserves a loopany record and routes it to the right artifact kind through a quality gate.

No licenceAuto-check passedAgent Workflows

Install Loopany Capture

skills CLI
$ npx skills add superdesigndev/loopany --skill loopany-capture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install superdesigndev/loopany loopany-capture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/superdesigndev/loopany.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/loopany-capture .claude/skills/loopany-capture && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
loopany-capture
GitHub stars
140
Token cost
~690 tokens
SKILL.md length
285 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
None found

At a glance

Decides, once a task is finished, whether the outcome deserves a loopany record and routes it to the right artifact kind through a quality gate.

  • Works in 5 steps: Filter — main session runs the quality… → Compose context (3-5 sentences): what… → Dispatch: "Record this via loopany. Read… → …
  • Recording the outcome after a pull request is merged
  • SKILL.md covers Event → Kind routing, Quality gate, Subagent dispatch and Anti-patterns
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

After substantive work wraps up, such as a shipped pull request, a resolved incident or a decision with a rationale, the agent checks whether a future reader would need to find the result. A routing table maps each event to a loopany artifact kind (task, signal or note), a short flowchart handles unclear cases, and note is the default when unsure.

A quality gate skips captures that are not observable, already recorded, too small, speculative or just internal agent work, with a quick test: if you cannot write a one-sentence outcome, skip it. The recording itself is handed to a subagent along with a few sentences of context so the main session keeps its focus. Hosts without subagents capture inline instead. The skill relies on the loopany command line and the loopany-core skill.

When your agent uses it

  • Recording the outcome after a pull request is merged
  • Logging a resolved incident along with what fixed it
  • Noting a decision and why one option was chosen over another
  • Flagging a problem you noticed but are deferring

Example prompts

  • “The PR for the retry logic just merged. Record the outcome.”
  • “Log this decision: we chose SQLite over Postgres for the local cache because setup is simpler.”
  • “Note that the flaky upload test is a problem we are leaving for next sprint.”

Requirements

  • The loopany CLI and the loopany-core skill

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Filter — main session runs the quality gate.
  2. Compose context (3-5 sentences): what happened, why it matters,
  3. Dispatch: "Record this via loopany. Read loopany-core to pick
  4. Subagent writes the artifact, returns ID.
  5. Main session continues — no context switch.

What it can do on your machine

Read from SKILL.md and the folder at commit cdd1d08. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Loopany Capture loads about 690 tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 285 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~690

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 285 words (~690 tokens).

“After substantive work concludes, check whether to record it as a loopany artifact. "Substantive" = produced evidence or a decision a future reader would need to find.”

— opening of SKILL.md by superdesigndev
name
loopany-capture

Read the full SKILL.md on GitHub

Files

Just SKILL.md in skills/loopany-capture of superdesigndev/loopany.

Open the folder on GitHubat commit cdd1d08

Compare with similar skills

Loopany Capture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Loopany Capture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Loopany Capture this skillsuperdesigndev/loopany140—~690Automated safety check: PassNone
Reflect on Session Learningscursor/plugins10k5 repos~1.2kAutomated safety check: PassNone
Create Agentvectorize-io/hindsight46k—~1.1kAutomated safety check: PassMIT
Ruflo Multi-Agent Orchestrationruvnet/ruflo74k1 repos~975Automated safety check: PassMIT
Weekly Project Digeststhedotmack/claude-mem97k—~3.5kAutomated safety check: PassApache-2.0
ArchonSethGammon/Citadel922—~5.4kAutomated safety check: PassMIT

Similar skills

  • Official

    Starts three parallel reviewer subagents over the current conversation transcript, then turns their findings into concrete edits to existing skills.

    10k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Create Agent

    vectorize-io/hindsight

    Create a new Hindsight-powered subagent with long-term memory.

    46k GitHub stars~1.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Sets up and drives Ruflo, an npm-installed orchestration layer for multi-agent swarms, persistent memory, routing, hooks and its MCP tool catalog.

    74k GitHub starsUsed in 1 repo~975 tokens
    Agent WorkflowsAuto-check passed
  • Weekly Project Digests

    thedotmack/claude-mem

    Turns a project's claude-mem timeline into a week-by-week narrative, splitting it by ISO week and running one subagent per week that receives the prior week's carry-forward block.

    97k GitHub stars~3.5k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Archon

    SethGammon/Citadel

    Autonomous multi-session campaign agent. An agent skill from SethGammon/Citadel.

    922 GitHub stars~5.4k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed
  • Forgetful MCP Client Setup

    ScottRBK/forgetful

    Connects an MCP client to the Forgetful memory server over stdio or HTTP, then confirms the link works with discovery and round-trip calls.

    301 GitHub stars~682 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from superdesigndev/loopany

  • loopany Periodic Review

    superdesigndev/loopany

    Runs a daily, weekly or monthly review of a loopany workspace, sorting items into silent fixes, things that need you and deferrals, and closing every surfaced item.

    140 GitHub stars~730 tokensUpdated 4 mo ago
    Auto-check passed
  • Loopany Artifact Lifecycle

    superdesigndev/loopany

    Routes artifact operations in a loopany workspace to the right playbook: tasks, signals, learnings, skill proposals, missions, people, notes, briefs and journals.

    140 GitHub stars~749 tokensUpdated 4 mo ago
    Auto-check passed
  • Loopany Reflect

    superdesigndev/loopany

    Runs a self-improvement loop for loopany: reads recent task outcomes and dismissed signals, finds patterns, writes learnings and skill proposals, and applies accepted ones.

    140 GitHub stars~1.4k tokensUpdated 4 mo ago
    Auto-check passed

Categories

Questions about Loopany Capture

What does Loopany Capture do?

Decides, once a task is finished, whether the outcome deserves a loopany record and routes it to the right artifact kind through a quality gate. After substantive work wraps up, such as a shipped pull request, a resolved incident or a decision with a rationale, the agent checks whether a future reader would need to find the result. A routing table maps each event to a loopany artifact kind (task, signal or note), a short flowchart handles unclear cases, and note is the default when unsure.

When should I use Loopany Capture?

Loopany Capture fits situations like: recording the outcome after a pull request is merged; logging a resolved incident along with what fixed it; noting a decision and why one option was chosen over another; flagging a problem you noticed but are deferring.

How do I install Loopany Capture in Claude Code?

Run `npx skills add superdesigndev/loopany --skill loopany-capture -a claude-code`. Or copy the skill folder (skills/loopany-capture in superdesigndev/loopany) into .claude/skills/loopany-capture in your project. Claude Code loads it when a task matches its description.

How do I install Loopany Capture in Codex?

Run `npx skills add superdesigndev/loopany --skill loopany-capture -a codex`. Or copy the skill folder (skills/loopany-capture in superdesigndev/loopany) into .agents/skills/loopany-capture in your project. Codex loads it when a task matches its description.

Can I use Loopany Capture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add superdesigndev/loopany --skill loopany-capture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/loopany-capture, .gemini/skills/loopany-capture, .github/skills/loopany-capture and .opencode/skills/loopany-capture in your project.

What does Loopany Capture need to run?

SKILL.md names no scripts, command-line tools or credentials: Loopany Capture is instructions for the agent only. Our summary lists: The loopany CLI and the loopany-core skill.

Does Loopany Capture access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Loopany Capture safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Loopany Capture use?

No licence was found for Loopany Capture or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Loopany Capture use?

About 690 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Loopany Capture?

Skills that share tags, products or a category with Loopany Capture: Reflect on Session Learnings (cursor/plugins, 10k stars), Create Agent (vectorize-io/hindsight, 46k stars), Ruflo Multi-Agent Orchestration (ruvnet/ruflo, 74k stars) and Weekly Project Digests (thedotmack/claude-mem, 97k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Loopany Capture?

superdesigndev (a GitHub organization) maintains it in superdesigndev/loopany, which has 140 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on June 2, 2026.

Source: superdesigndev/loopany on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.