competitor-edge-strategist
Skill1 starsChanged 23 days agoNo licenceView on GitHub
Deep competitive and customer research for the product in the current repo. Reads the whole codebase to understand what is being built, researches the internet in depth to find competitors, why and how they offer what they offer, what real customers complain about and need, researches which open-source projects and libraries we can adopt to make the product flourish (with license, health and security checks), generates many ideas and then argues them out in a structured internal debate (proposer vs skeptic vs customer vs engineer, with an evidence ledger and a verdict for each idea), designs a "competitors but better" strategy built on small solutions to big problems, and writes a full strategy report, a debate log, plus a ready-to-paste prompt for a Manager agent to turn into a complete execution plan. Use this skill whenever the user asks about competitors, market research, differentiation, positioning, "how do we beat X", "what should we build next", product strategy, customer pain points, feature ideas, roadmap ideas, open-source tools to use, wants ideas stress-tested or debated, or wants a plan/prompt for a manager agent, even if they never say "competitor" explicitly.
In this repository12 other files it gives its agents.
- devils-advocate-reviewerSkill
- dsa-logic-builderSkill
- lazy-senior-engineerSkill
- master-frontend-engineerSkill
- pessimistic-minimalist-backendSkill
- pessimistic-minimalist-frontend-engineerSkill
- precision-code-reviewerSkill
- product-uiSkill
- project-managerSkill
- project-orchestratorSkill
- skill-forgeSkill
- swmr-agent-logSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 14 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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
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.