Agent Skills

---

name: mcp-attribution-worktree

description: Triage, repair, and close MCP attribution issues from the local report API with evidence-driven decisions and isolated Worktrunk worktrees. Use this skill when Codex needs to process `tool` attribution issues and skills-related attribution issues, inspect related runs, decide whether the issue is actionable in `mcp/src` or `config/source/skills`, update attribution fields as `owner=codex`, and then complete the fix loop through GitHub issue tracking, worktree-based code changes, PR submission, and follow-up iteration when the problem is repairable.

---

name: planning-workflows

description: Spec and no-spec planning workflows derived from local slash commands (requirements, design, tasks).

---

name: pr-review-fix

description: Periodically analyze open pull requests for CI failures, code review feedback, and quality issues, then fix them in batch. Use this skill when the user asks to check PR status, triage CI failures, fix review comments, analyze open PRs, or run a scheduled PR health check across the repository.

---

name: review-automation-orchestrator

description: Use when running or scheduling periodic repository review cycles that must dispatch the correct reviewer, aggregate findings, and escalate outcomes into reports, issues, or corrective PRs across API contracts, documentation freshness, code quality, and CloudBase skill quality.

---

name: skill-authoring

description: Design, improve, and evaluate reusable agent skills with high-quality SKILL.md files, precise trigger descriptions, progressive disclosure, and testable behavior. This skill should be used when users ask to create a new skill, rewrite or review an existing skill, audit a skill collection such as `config/source/skills` for redundancy or overlap, improve skill trigger quality, organize skill references, or evaluate whether a skill should trigger and behave correctly.

---

name: api-conventions

description: API design patterns and conventions for this project. Covers RESTful URL naming, response format standards, error handling, and authentication requirements. Use when writing or reviewing API endpoints, designing new APIs, or making decisions about request/response formats.

---

name: api-documenting

description: Generate API documentation from code. Use when the user wants to document APIs, create API reference, generate endpoint documentation, or needs help with OpenAPI/Swagger specs.

---

name: api-documenting

description: Generate API documentation from code. Use when the user wants to document APIs, create API reference, generate endpoint documentation, or needs help with OpenAPI/Swagger specs.

---

name: api-generating

description: Generate API endpoint documentation from Express route files. Use when the user asks to generate, update, or review API docs for Express.js routes.

---

name: api-generating

description: Generate API endpoint code and documentation from specifications. Use when the user wants to create new API endpoints, generate route handlers, scaffold REST APIs, or produce OpenAPI/Swagger specs from code.

---

name: api-generating

description: Generate API endpoint code and documentation from specifications. Use when the user wants to create new API endpoints, generate route handlers, scaffold REST APIs, or produce OpenAPI/Swagger specs from code.

---

name: codebase-visualizer

description: Generate an interactive tree visualization of your codebase. Use when exploring a new repo or understanding project structure.

---

name: codebase-visualizer

description: Generate an interactive tree visualization of your codebase. Use when exploring a new repo or understanding project structure.

---

name: code-health-check

description: Perform a comprehensive code health check on a directory. Use when the user asks to analyze code quality, find issues, or get a health report.

---

name: code-reviewing

description: Review code for quality, security, and best practices. Use when the user asks for code review, wants feedback on their code, mentions reviewing changes, or asks about code quality.

---

name: code-reviewing

description: Review code for quality, security, and best practices. Use when the user asks for code review, wants feedback on their code, mentions reviewing changes, or asks about code quality.

---

name: doc-writing

description: Generate API documentation from a route manifest. Use when you have a list of discovered routes and need to produce markdown documentation.

---

name: financial-analyzing

description: Analyze financial data, calculate financial ratios, and generate analysis reports. Use when the user asks about revenue, costs, profits, margins, ROI, financial metrics, or needs financial analysis of a company or project.

---

name: financial-analyzing

description: Analyze financial data, calculate financial ratios, and generate analysis reports. Use when the user asks about revenue, costs, profits, margins, ROI, financial metrics, or needs financial analysis of a company or project.

---

name: quality-checking

description: Validate API documentation against quality standards. Use when you need to verify generated docs are complete and correct.

---

name: React 最佳实践

description: React 组件设计模式、Hooks 使用指南、性能优化技巧

---

name: route-scanning

description: Scan Express.js source files to discover all API route definitions.

---

name: affiliate-marketing-strategy

---

name: api-monitoring