AGENT SKILL

agent-task-mapping

Map tasks to specialist agents. Use when choosing which agent for a job, comparing agent capabilities, or routing to React/Next.js/Playwright/docs/code-quality experts. Keywords: which agent, best agent for this, delegate to expert, agent capability mapping.

License 许可
MIT
所属仓库
bg-szy/TOP-SKILLS
最近更新
2026-11-15
Stars
★ 6
Forks
0

01 前言 Front Matter

name
agent-task-mapping
tags
[ "task", "mapping", "agents", "delegation", "workflow" ]
version
2.0
description
Map tasks to specialist agents. Use when choosing which agent for a job, comparing agent capabilities, or routing to React/Next.js/Playwright/docs/code-quality experts. Keywords: which agent, best agent for this, delegate to expert, agent capability mapping.
last_updated
1788825600000

02 资源文件 2

03 SKILL.md 正文

Agent Task Mapping

  • Leverage native parallel subagent dispatch and 200k+ context windows where available.

Activation Conditions

Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.

Use this skill when:

  • Determining which specialized agent to delegate a task to
  • Reviewing agent capabilities and expertise areas
  • Trying to match a specific task to an appropriate specialist
  • Needing quick reference for available agents and their purposes

Available Agents

See Agent Details for comprehensive information about each agent:

  • Description and specialization areas
  • When to use each agent
  • Typical tasks handled by each

<!-- MCP:START -->

<!-- PORTABILITY:START -->

Cross-Client Portability

This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.

  • GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the workflow in project instructions when folder discovery is unavailable.
  • Claude Code: keep the folder in a local skills directory or a compatible plugin source.
  • Codex: install or sync the folder into $CODEX_HOME/skills/agent-task-mapping and restart Codex after major changes.

<!-- PORTABILITY:END -->

MCP Availability And Fallback

Preferred MCP Server: None required

  • Fallback prompt: "Use the Agent Task Mapping skill without MCP. Rely on its local instructions, bundled resources, standard shell or editor tools, and direct verification. Show the evidence used before concluding."
  • Do not claim an MCP operation was used when the active host does not expose it.
  • Treat local files, tests, rendered outputs, logs, or screenshots as the fallback evidence path.

<!-- MCP:END -->

Anti-Patterns

  • Delegating or evaluating without a scoped success condition: The output becomes hard to review and easy to overbuild.
  • Skipping the evidence step: A workflow that cannot be re-checked quickly is not ready for handoff.
  • Bundling unrelated subtasks together: It creates noisy prompts, weaker ownership, and avoidable integration risk.

Verification Protocol

Before claiming "skill applied successfully":

  1. Pass/fail: The Agent Task Mapping workflow names the agent boundary, delegated scope, and expected return artifact.
  2. Pass/fail: Context passed to helpers is minimal, task-local, and free of hidden expected answers.
  3. Pass/fail: Results are integrated only after evidence, diffs, or citations are checked by the controller.
  4. Pressure-test scenario: Run the workflow on two similar tasks that must not share assumptions or leaked context.
  5. Success metric: Zero context leakage; every delegated output is independently reviewable.

Examples & Scripts

Quick Reference

Agent Name Best For
Code Explainer Analyzing and documenting existing code
UI Designer UI/UX improvements and design implementations
Universal Janitor Code cleanup, simplification, and tech debt removal
Critical Thinking Challenging assumptions and exploring alternatives
Next.js Expert Next.js 15/16+ architecture and optimizations
Expert React Frontend Engineer React 19+ patterns and best practices
Playwright Tester Mode Comprehensive testing with exploratory testing
Tech Writer Creating formal developer documentation
Create PRD Chat Mode Generating Product Requirements Documents
Specification Generating or updating specification documents
Plan Research and outlining multi-step plans

Decision Framework

When choosing an agent for delegation:

  1. Identify task type: Is it documentation, testing, two-stage review (spec compliance first, then code quality), or development?
  2. Match to specialization: Find agent whose description aligns with task
  3. Check availability: Verify agent exists and has proper frontmatter configuration
  4. Use specific agentName: Delegate using exact name from agent's frontmatter

Task Categories

Code Analysis & Documentation

  • Use Code Explainer for analyzing existing code patterns
  • Use Tech Writer for formal developer documentation
  • Use Specification for generating feature specifications

Code Quality & Maintenance

  • Use Universal Janitor for cleanup and tech debt remediation
  • Use Critical Thinking for challenging assumptions

Development Work

  • Use Next.js Expert for Next.js 15/16+ architecture and optimizations
  • Use Expert React Frontend Engineer for React 19+ patterns

Testing

  • Use Playwright Tester Mode for comprehensive web application testing

Planning & Requirements

  • Use Plan for research and outlining multi-step plans
  • Use Create PRD Chat Mode for generating Product Requirements Documents

Design

  • Use UI Designer for UI/UX improvements and design implementations

Related Skills

  • custom-agent-usage: Use it when the workflow also needs loading and invoking custom agent definitions safely.
  • subagent-delegation: Use it when the workflow also needs safe, scoped delegation to helper agents.
  • subagent-driven-development: Use it when the workflow also needs plan-driven implementation with reviewer loops.
  • agentic-eval: Use it when the workflow also needs rubric-driven evaluation loops.

04 同仓库更多 Skills

bg-szy
bg-szy/TOP-SKILLS

serpmaven

Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-landing-page-audit

Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-growth-context

Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-get-listed

Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-ai-readiness-audit

Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

proxy-troubleshooting

Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.

★ 6