agentleFS
Sign inStart free
d-o-hubd-o-hub/github-template-ai-agents/.agents/skills/delegate/SKILL.md

delegate

Skill2 starsChanged 10 days agoMITView on GitHub

Lightweight retrieval and context agent skill for rapid information gathering and environment assessment. Use this skill when you need quick context lookups, finding code patterns, or assessing current state without full implementation overhead — even if they just say "find where X is defined" or "what's the current state of Y".

78 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use state, preview 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.
  • MicrosoftSkill

    state

    Store and query a Microsoft Managed App's built-in state and file attachments with `ms project state` CLI schema commands and generated TypeScript clients. First, with the user signed in to the CLI, run `ms feature status --name state --json`; if `feature.enabled` is not `true`, recommend an alternative connector or data source.

    Also in 3 projects that use this

  • kv0906Skill

    preview

    Render vault notes as styled HTML and open in browser. Turn markdown docs, decisions, progress reports into readable previews. Use for "/preview docs/project-a/checkout-flow.md", "/preview progress all", "/preview decide auth-approach", or when user wants to see a doc before sharing.

    Also in 3 projects that use this

  • GitHubSkill

    prd

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

    Also in 5 projects that use this

  • nicolasestremSkill

    document

    Create focused documentation for specific components or features

    Also in 3 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    skill-authoring

    Write Agent Skills that comply with the agentskills.io specification. WHEN: "create a skill", "new skill", "write a skill", "skill template", "skill structure", "review skill", "skill PR", "skill compliance", "SKILL.md format", "skill frontmatter", "skill best practices". DO NOT USE FOR: general documentation. INVOKES: vally CLI.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Context Retrieval: Use grep and glob to locate files matching the query.

    line 26
  2. Distinctive:

    Summarization: Read relevant files and synthesize findings into a concise summary.

    line 27
  3. Distinctive:

    Avoid deep file reads when a targeted grep would suffice — saves tokens and context.

    line 49
  4. Distinctive:

    When searching for patterns, use the narrowest regex possible to avoid noise.

    line 50
  5. Distinctive:

    If the query is ambiguous, retrieve first, then ask for clarification with context.

    line 51

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

Delegate Skill

The Delegate skill provides a lightweight tier for rapid retrieval and context gathering.

When to Use

  • Quick context lookups and pattern matching
  • Finding specific code implementations or documentation
  • Assessing the current state of a repository before planning
  • Identifying potential areas for modification without deep analysis
  • Even if they just say "find where X is defined" or "what's the current state of Y"

Workflow

  1. Context Retrieval: Use grep and glob to locate files matching the query.
  2. Summarization: Read relevant files and synthesize findings into a concise summary.
  3. Handoff: Pass gathered context to the primary agent or an Implementer.

What to Retrieve

Query TypeToolsExample
"Where is X defined?"grep -rn "def X|class X|function X"Find function/class definitions
"What uses X?"grep -rn "import X|require.*X|from X"Find all consumers of a module
"Show me the structure"find . -type f -name "*.py" | head -30Map directory layout
"What changed recently?"git log --oneline -10Recent commit history
"What's in this config?"Read the file directlyParse configuration files

When to Hand Off

Delegate should hand off to an Implementer when:

  • The task requires modifying code, not just reading it
  • The user's intent is clearly "fix" or "change" rather than "find" or "show"
  • The retrieved context reveals a bug or issue that needs a code fix

Gotchas

  • Avoid deep file reads when a targeted grep would suffice — saves tokens and context.
  • When searching for patterns, use the narrowest regex possible to avoid noise.
  • If the query is ambiguous, retrieve first, then ask for clarification with context.

Rationalizations

RationalizationReality
"I can find this faster myself"Using the Delegate skill ensures systematic coverage and reduces cognitive load during discovery.
"Just grep for it inline"Structured retrieval with handoff ensures findings are captured and passed to the right agent.

Red Flags

  • Modifying files while in a "Delegate" context
  • Spending too much time on retrieval when implementation is the goal
  • Reading entire files when targeted grep would answer the question

See Also

  • implementer — Execute code changes after delegation
  • goap-agent — Orchestrator that uses delegate for context gathering

Voice & Context

  • Default: professional + blog
  • Reference: voice-profiles skill for definitions and auto-detection.

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.

Check your setup, free