Menu
Correct naming for a PR
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Agent eXperience Interface (AXI) router — the main entry point for agent-ergonomic CLIs. Use whenever the agent needs GitHub, browser automation, human review, quota routing, Slack, Notion, AWS/Docker/K8s, databases, or any AXI-catalog tool; when choosing AXI vs MCP vs raw CLI; when building or reviewing an agent-facing CLI; or when the user says axi, gh-axi, chrome-devtools-axi, TOON output, agent ergonomics, or "prefer AXI". When in doubt about which external tool interface to use, start here.
A senior marketing operator for any project. Orchestrates 64 marketing skills to build brands, generate content, and distribute across channels. Use this skill whenever the user wants to do marketing - brand voice, copy, SEO, email, social, launches, or anything marketing-related. Also triggers on 'help me market', 'write copy', 'launch strategy', 'brand voice', 'SEO', 'content', 'email sequence', 'social posts', 'landing page', 'grow', 'audience', 'competitors', 'what should I do next for marketing', 'I need more users', 'how do I get people to care', or any marketing request. When in doubt about which marketing skill to use, start here - even if the user's request is vague or doesn't explicitly mention marketing.
Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.
Research and analyze competitors to find positioning gaps and strategic opportunities. Use this skill whenever the user mentions competitors, competitive analysis, competitor teardown, market landscape, 'who else does this', 'how are we different', or competitor research. Also trigger when the user is entering a new market, when positioning feels weak or generic, when preparing for a launch, when any downstream skill needs competitors.md but it doesn't exist, or when the user asks about differentiation or market gaps. Even if the user just names a competitor casually ('what does X do?'), this skill likely applies. Three modes: Quick Scan, Deep Teardown, Gap Finder.
Scan the current market landscape and produce a ground-truth ecosystem snapshot. Chains /last30days for live research, validates with user, and writes brand/landscape.md with a Claims Blacklist that hard-gates all content generation. Use when: "landscape", "ecosystem", "market snapshot", "ground truth", "what's happening", "refresh landscape", "market trends", or before any content campaign to verify claims.
Build applications and agents with Exa's API Platform: search, contents, answer, context, Agent API, monitors, websets, OpenAI-compatible endpoints, and exa-py / exa-js. Use when choosing Exa endpoints, writing Exa API calls, integrating semantic web search or research into products, or debugging Exa request shapes. Load references/ on demand for endpoint details.
| name | pr-name |
| description | Correct naming for a PR |
The following format must be used for the PR title:
`[package-name]`: [commit-message]
For example:
`@remotion/shapes`: Add heart shape
The package name must be obtained from package.json.
If multiple packages are affected, use the one that you think if most relevant.
If the change is about docs only:
Docs: Add page about heart shape