Agent skill

Compound

by team-attention in team-attention/hoyeon

This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR.

MITAuto-check: notes

Install Compound

skills CLI
$ npx skills add team-attention/hoyeon --skill compound -a claude-code

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

GitHub CLI
$ gh skill install team-attention/hoyeon compound --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/team-attention/hoyeon.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/compound .claude/skills/compound && 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
compound
GitHub stars
173
Token cost
~1.1k tokens
SKILL.md length
325 words
Files
3 (incl. references)
Skills in repo
36
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR.

  • Works in 3 steps: Context Collection → Knowledge Extraction & Classification → Document Generation
  • Document learnings
  • SKILL.md covers Workflow, Usage Examples and Output
  • Calls gh

What it does

Compound is an agent skill from team-attention/hoyeon. This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR. Extracts knowledge from PR context and saves to docs/learnings/.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/problem-types.md` and `templates/LEARNING_TEMPLATE.md`).

The repository describes itself as: Requirements-first Harness — derive, verify, execute. The licence is MIT.

When your agent uses it

  • Document learnings
  • Save what we learned
  • After completing a PR

Example prompts

  • “/compound”
  • “compound this”
  • “document learnings”
  • “/compound”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash, Write, Edit, AskUserQuestion

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Context Collection
  2. Knowledge Extraction & Classification
  3. Document Generation

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Bash
    • Write
    • Edit
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    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

Compound loads about 1.1k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 55 tokens; SKILL.md has 325 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

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

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Bash, Write, Edit, AskUserQuestion

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

The full file from team-attention/hoyeon at commit 7cff032, republished under its MIT licence (© team-attention). 325 words, ~1,062 tokens.

Download SKILL.mdSave it as .claude/skills/compound/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
compound
description
This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR. Extracts knowledge from PR context and saves to docs/learnings/.
allowed-tools
Read, Grep, Glob, Bash, Write, Edit, AskUserQuestion

Compound Skill

Extracts knowledge from PR context and saves structured documentation to docs/learnings/.

Workflow

Phase 1: Context Collection
  1. Identify PR number/branch

    • Use PR number if provided as argument
    • Otherwise, find PR from current branch: gh pr view --json number,body,title
    • If no PR exists: Prompt user to enter PR number directly or confirm proceeding without PR
  2. Extract Plan path

    • Find Plan path pattern in PR body: .hoyeon/specs/{name}/PLAN.md
    • Regex: \.hoyeon/specs/[^/]+/PLAN\.md
    • If no Plan path found: Prompt user to enter spec name directly or select from .hoyeon/specs/ directory listing
  3. Derive Context path

    • Extract spec name from Plan path
    • Context directory: .hoyeon/specs/{name}/context/
  4. Parallel collection (run following commands simultaneously, skip if files don't exist)

    bash
    # Context files (treat as empty if not found)
    cat .hoyeon/specs/{name}/context/learnings.json 2>/dev/null || echo ""
    cat .hoyeon/specs/{name}/context/decisions.md 2>/dev/null || echo ""
    cat .hoyeon/specs/{name}/context/issues.json 2>/dev/null || echo ""
    
    # PR comments and reviews (collect as JSON for stability)
    gh pr view {pr_number} --json comments,reviews

Error Handling:

  • If no context files exist AND no PR comments → Notify user and request manual input
  • At least 1 source required to proceed with document generation
Phase 2: Knowledge Extraction & Classification
2.1 Extract Valuable Feedback from PR Comments

Criteria for valuable feedback:

  • Code improvement suggestions
  • Bug/issue identification
  • Pattern/best practice mentions
  • "This would be better" type advice
  • Comments left with approval

Filter out:

  • Simple questions ("What is this?")
  • Confirmation requests ("Is this correct?")
  • Approval-only comments ("LGTM", "Approved")
  • Bot comments

Extraction keywords:

  • "suggest", "recommend", "better", "instead"
  • "pattern", "practice", "convention"
  • "issue", "bug", "fix"
  • "learned", "TIL", "note"

Extracted information:

  • author
  • body
  • file_path (if inline comment)
  • created_at
Show full SKILL.md (140 more words)Show less
2.2 Analyze Context Files
FilePurpose
learnings.jsonStructured learnings
decisions.mdDecision rationale
issues.jsonStructured issues
2.3 Synthesize
  1. Assess documentation value from collected sources
  2. Check for duplicates: Search docs/learnings/
  3. Classify problem type - Refer to references/problem-types.md (relative to this skill directory)
  4. Generate tags
Phase 3: Document Generation
  1. Generate YAML frontmatter

    yaml
    pr_number: {PR_NUMBER}
    date: {YYYY-MM-DD}
    problem_type: {TYPE}
    tags: [{TAGS}]
    plan_path: {PLAN_PATH}
  2. Write document using template

    • Template location: templates/LEARNING_TEMPLATE.md (relative to this skill directory)
    • Read template and substitute placeholders
  3. Determine filename

    • Format: {YYYY-MM-DD}-{short-title}.md
    • Example: 2024-01-15-api-error-handling.md
  4. Save

    • Path: docs/learnings/{filename}.md
  5. Add cross-references (if related documents exist)

    • Add new document link to Related section of existing documents

Usage Examples

# Specify PR number
/compound 123

# Use PR from current branch
/compound

Output

Outputs the created document path and summary:

Created: docs/learnings/2024-01-15-api-error-handling.md

Summary:
- Problem Type: error-handling
- Tags: api, typescript, validation
- Sources: learnings.json, 2 PR comments

<!-- TODO: Future extensions -->
<!-- - [ ] Session ID based user feedback collection -->
<!-- - [ ] CLAUDE.md auto-update suggestions -->
<!-- - [ ] Detect existing document UPDATEs -->
<!-- - [ ] Auto-categorization by problem_type (docs/solutions/{type}/) -->

© team-attention, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/compound of team-attention/hoyeon.

  • SKILL.md
  • references/problem-types.md
  • templates/LEARNING_TEMPLATE.md

Open the folder on GitHubat commit 7cff032

Compare with similar skills

Compound 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.

Compound compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Compound this skillteam-attention/hoyeon173—~1.1kAutomated safety check: NotesMIT
Compoundoliver-kriska/claude-elixir-phoenix565—~964Automated safety check: PassMIT
Compoundm-xlsea/ruoyi-plus-soybean328—~280Automated safety check: PassMIT
Compoundgaragon/nanostack207—~2.2kAutomated safety check: PassApache-2.0
Compoundthoreinstein/gemini-obsidian102—~454Automated safety check: PassISC
Compound Learning WriterEveryInc/compound-engineering-plugin25k—~2kAutomated safety check: PassMIT

Similar skills

  • Compound

    oliver-kriska/claude-elixir-phoenix

    Capture solved problems as searchable solution docs. An agent skill from oliver-kriska/claude-elixir-phoenix.

    565 GitHub stars~964 tokensUpdated 2 days ago
    SecurityAuto-check passed
  • Compound

    m-xlsea/ruoyi-plus-soybean

    Sprint Quality Gate 通过后触发。提炼本 Sprint 学到的为结构化条目追加 lessons.md。

    328 GitHub stars~280 tokensUpdated 3 mo ago
    Testing & QAAuto-check passed
  • Compound

    garagon/nanostack

    Document what you learned during this sprint. An agent skill from garagon/nanostack.

    207 GitHub stars~2.2k tokensUpdated 28 days ago
    Auto-check passed
  • Compound

    thoreinstein/gemini-obsidian

    A skill your agent uses when the user wants to promote cross-project knowledge to the global Engineering/ folder, or says "promote knowledge", "compound notes", "knowledge synthesis", or "find…

    102 GitHub stars~454 tokensUpdated 2 mo ago
    Auto-check passed
  • Compound Learning Writer

    EveryInc/compound-engineering-plugin

    Records one solved and verified problem as a durable learning in the repository, but only when the reasoning is not already clear from the final code, tests or docs.

    25k GitHub stars~2k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Compound Learnings Refresh

    EveryInc/compound-engineering-plugin

    Audits a repo's stored learnings against the current codebase, fixes stale, overlapping or superseded docs and reports on every document.

    25k GitHub stars~2k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from team-attention/hoyeon

All 36 skills in this repo
  • Skill Session Analyzer

    team-attention/hoyeon

    This skill should be used when the user asks to "analyze session", "evaluate skill execution", "check session logs", provides a session ID with a skill path, or wants to verify that a skill executed…

    173 GitHub stars~1.9k tokensUpdated 4 mo ago
    Auto-check: notes
  • Browser Work

    team-attention/hoyeon

    Recon-first browser automation. An agent skill from team-attention/hoyeon.

    173 GitHub stars~1.9k tokensUpdated 4 mo ago
    Auto-check passed
  • Check

    team-attention/hoyeon

    This skill should be used when the user wants to verify their changes before pushing, or update the project's rule checklists.

    173 GitHub stars~1.8k tokensUpdated 4 mo ago
    Auto-check: notes
  • QA

    team-attention/hoyeon

    Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen.

    173 GitHub stars~2.6k tokensUpdated 4 mo ago
    Auto-check: notes
  • Dev Scan

    team-attention/hoyeon

    Collect diverse opinions on technical topics from developer communities.

    173 GitHub starsUsed in 1 repo~5k tokens
    Auto-check passed
  • Tech Decision

    team-attention/hoyeon

    This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use"…

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

Questions about Compound

What does Compound do?

This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR. Compound is an agent skill from team-attention/hoyeon. This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR.

When should I use Compound?

Compound fits situations like: document learnings; save what we learned; after completing a PR.

How do I install Compound in Claude Code?

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

How do I install Compound in Codex?

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

Can I use Compound 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 team-attention/hoyeon --skill compound -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/compound, .gemini/skills/compound, .github/skills/compound and .opencode/skills/compound in your project.

What does Compound need to run?

Going by SKILL.md and its folder, Compound needs the command-line tools its instructions call (gh). Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash, Write, Edit, AskUserQuestion.

Does Compound access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Compound safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Compound use?

Compound is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Compound use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 717 tokens, read only when the agent opens those files.

What are the alternatives to Compound?

Skills that share tags, products or a category with Compound: Compound (oliver-kriska/claude-elixir-phoenix, 565 stars), Compound (m-xlsea/ruoyi-plus-soybean, 328 stars), Compound (garagon/nanostack, 207 stars) and Compound (thoreinstein/gemini-obsidian, 102 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Compound?

team-attention (a GitHub organization) maintains it in team-attention/hoyeon, which has 173 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on May 21, 2026.

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