New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Skill Intake

by nyldn in nyldn/claude-octopus

Move incoming issues and pull requests through triage states until each is actionable or closed — use when the queue has piled up or a report arrives unsorted

MITAuto-check passedDevelopment

Install Skill Intake

skills CLI
$ npx skills add nyldn/claude-octopus --skill skill-intake -a claude-code

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

GitHub CLI
$ gh skill install nyldn/claude-octopus skill-intake --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/nyldn/claude-octopus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-intake .claude/skills/skill-intake && 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
skill-intake
GitHub stars
4.2k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
812 words
Files
2
Skills in repo
62
Repo updated
First seen
Licence
MIT

At a glance

Move incoming issues and pull requests through triage states until each is actionable or closed — use when the queue has piled up or a report arrives unsorted

  • Works in 5 steps: Categorise → Verify → Assign a state → …
  • The queue has piled up
  • SKILL.md covers When To Use, When Not To Use, Inputs and Workflow, plus 4 more sections
  • Calls gh

What it does

Skill Intake is an agent skill from nyldn/claude-octopus. Move incoming issues and pull requests through triage states until each is actionable or closed — use when the queue has piled up or a report arrives unsorted

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Pull requests. The repository describes itself as: Run multiple AI models against the same research, design, or coding task. Surface disagreements before you ship. The licence is MIT.

When your agent uses it

  • The queue has piled up
  • A report arrives unsorted

Example prompts

  • “/skill-intake”

Workflow steps

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

  1. Categorise
  2. Verify
  3. Assign a state
  4. Write the brief
  5. Record it

What it can do on your machine

Read from SKILL.md and the folder at commit 4d152db. 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

    Shell commands in SKILL.md call:

    • gh

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

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    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

Skill Intake loads about 1.4k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 812 words of instructions outside code blocks.

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

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

The full file from nyldn/claude-octopus at commit 4d152db, republished under its MIT licence (© nyldn). 812 words, ~1,374 tokens.

Download SKILL.mdSave it as .claude/skills/skill-intake/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
skill-intake
description
Move incoming issues and pull requests through triage states until each is actionable or closed — use when the queue has piled up or a report arrives unsorted
disable-model-invocation
true

Host: Codex CLI — This skill was designed for Claude Code and adapted for Codex. Cross-reference commands use installed skill names in Codex rather than /octo:* slash commands. Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it. For host tool equivalents, see skills/blocks/codex-host-adapter.md.

Intake

Work the incoming queue. Each item moves through a small set of states until it is either actionable by someone who did not write it, or closed with a reason.

A pull request is an issue with attached code. Same states, same moves, with the deltas noted below. Resolving a bare #42 means checking both.

Adapted from triage in mattpocock/skills (MIT), cut down to the states this repo can actually represent and retargeted at gh and bd.

When To Use

  • Open issues or PRs have accumulated and nobody knows which are real.
  • A new report arrives and needs sorting before anyone works it.
  • An issue has been sitting because it is not clear what it is asking for.
  • Before planning, to establish what is actually in the queue.

When Not To Use

  • To do the work an item describes. Triage decides what happens to it, not how.
  • For local, private notes. That is skill-issues and .octo/ISSUES.md.
  • To review a PR's code quality. That is skill-code-review or skill-staged-review; intake decides whether the PR should be reviewed at all.

Inputs

An issue or PR reference, or nothing — with nothing, take the queue in order. gh issue list and gh pr list for the public surface; bd ready and bd blocked for tracked work.

Workflow

1. Categorise

What kind of thing is it: a bug, an enhancement, a question, or noise. For a PR, also: does it correspond to an existing issue, or arrive unannounced?

Do not skip this because the title looks obvious. Titles are written by people who already know what they meant.

2. Verify

The step that earns the whole skill. For a bug: reproduce it, or establish that you cannot. For a PR: check the claim it makes is the change it contains.

An unverified bug report is a hypothesis. Filing it as fact wastes whoever picks it up. If reproduction needs something you do not have — credentials, a dataset, a platform — that is needs-info, not verified.

3. Assign a state
  • needs-triage — arrived, not yet sorted. The entry state.
  • needs-info — blocked on the reporter. Say exactly what is missing; "more detail" is not a request anyone can act on.
  • verified — reproduced or confirmed, ready to be worked.
  • needs-decision — real, but what to do is a judgement call the maintainer has not made. Do not resolve these by inference. Escalate, or run skill-pressure-test with the maintainer.
  • closed — not a bug, out of scope, duplicate, or fixed. Always with a reason, and for out-of-scope, why.
Show full SKILL.md (339 more words)Show less
4. Write the brief

For anything reaching verified, write what someone picking it up needs and would otherwise have to rediscover: where the relevant code is, what you already ruled out, and how to tell when it is fixed. This is the difference between an item that gets worked and one that gets re-triaged.

For a PR, add: whether it has tests, whether CI is green, and whether it conflicts with anything in flight.

5. Record it

For public comment text, stream the completed note through the outbound gate:

bash
printf '%s\n' "$TRIAGE_NOTE" | \
  "${CLAUDE_PLUGIN_ROOT:-${HOME}/.claude-octopus/plugin}/scripts/safe-gh-comment.sh" \
    --repo OWNER/REPO issue-comment ISSUE_NUMBER -

Use gh issue edit --add-label only for the label mutation. Use bd update for tracked work. If bd writes are blocked by pending migrations, say so and do not run the migration — see skill-work-slicing for that constraint.

Provider Or Data Priority

  1. The repository — reproduce against the actual code.
  2. CI logs and run history for anything claiming a failure.
  3. The reporter, for what only they can supply.
  4. Never assume the report is accurate because it is detailed.

Stop Or Checkpoint Rules

  • Stop before closing anything a human filed deliberately, unless it is a clear duplicate. Closing is the one move that is rude to get wrong.
  • Stop before needs-decision items and surface them rather than guessing.
  • Do not merge or push as part of triage, even for a PR that looks ready.
  • One item at a time. Batch-labelling a queue without reading it is how real reports end up buried under a label.

Output Contract

Per item:

  1. Reference and category.
  2. State assigned, and why.
  3. Verification result — reproduced, could not reproduce, or not attempted with the reason.
  4. Brief — for verified items only.
  5. Action taken — labels, comments, or the exact commands not run and why.

Then a queue summary: counts by state, and which items are now takeable.

Verification

  • Every verified item was actually reproduced, or says explicitly that it was not and why.
  • Every needs-info names the specific missing thing.
  • Every closure carries a reason.
  • Nothing was merged, pushed, or fixed during triage.

© nyldn, 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 1 other file in skills/skill-intake of nyldn/claude-octopus.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 4d152db

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in nyldn/claude-octopus, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Skill Intake 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.

Skill Intake compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Skill Intake this skillnyldn/claude-octopus4.2k1 repos~1.4kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from nyldn/claude-octopus

All 62 skills in this repo

  • Octopus Quick

    nyldn/claude-octopus

    Quick execution for ad-hoc tasks without full workflow overhead — use for small, self-contained requests

    4.2k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed

  • Octopus Research

    nyldn/claude-octopus

    Thorough research across multiple sources — use for complex topics needing broad synthesis

    4.2k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Octopus Security Audit

    nyldn/claude-octopus

    OWASP compliance, vulnerability scanning, and adversarial red team testing — use for security reviews

    4.2k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Skill Audit

    nyldn/claude-octopus

    Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review

    4.2k GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed

  • Skill Content Pipeline

    nyldn/claude-octopus

    Extract patterns and anatomy from URLs — use to reverse-engineer content strategies from live pages

    4.2k GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed

  • Skill Context Detection

    nyldn/claude-octopus

    Auto-detect work context (Dev vs Knowledge) — use to tailor workflows based on current task type

    4.2k GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed

Categories

Questions about Skill Intake

What does Skill Intake do?

Move incoming issues and pull requests through triage states until each is actionable or closed — use when the queue has piled up or a report arrives unsorted. Skill Intake is an agent skill from nyldn/claude-octopus.

When should I use Skill Intake?

Skill Intake fits situations like: the queue has piled up; A report arrives unsorted.

How do I install Skill Intake in Claude Code?

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

How do I install Skill Intake in Codex?

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

Can I use Skill Intake 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 nyldn/claude-octopus --skill skill-intake -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-intake, .gemini/skills/skill-intake, .github/skills/skill-intake and .opencode/skills/skill-intake in your project.

What does Skill Intake need to run?

Going by SKILL.md and its folder, Skill Intake needs the command-line tools its instructions call (gh).

Does Skill Intake access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Skill Intake 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 Skill Intake use?

Skill Intake 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 Skill Intake use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Skill Intake?

Skills that share tags, products or a category with Skill Intake: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Skill Intake?

nyldn (a GitHub user) maintains it in nyldn/claude-octopus, which has 4,182 GitHub stars. The repository holds 62 skills in this directory. The repository was last updated on October 7, 2026.

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