competitive
Skill0 starsChanged 8 months agoMITView on GitHub
Competitive move response. Detects and analyzes competitor actions (pricing, launches, partnerships), assesses cross-department impact, drafts response plan. Triggered as needed. Octopus colors: Yellow (intelligence) + Purple (impact assessment) + Green (response).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- agentmart/pm-ostheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- agentmart/pm-os★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read .chairman/config.json and relevant department knowledge bases
- Distinctive: line 17
Verify the information: is this confirmed or rumor?
- Distinctive: line 61
Do not overreact. Most competitor moves do not require a response.
- Distinctive: line 62
Verify before escalating. Rumors are not actionable intelligence.
- Very specific: line 63
If responding, draft is for Chairman review only.
- Distinctive: line 65
Update marketing knowledge base with competitor intel
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
/competitive: Competitive Move Response
Octopus Colors: Yellow (Researcher) + Purple (Manager) + Green (Marketer)
Process
- Read
.chairman/config.jsonand relevant department knowledge bases - Gather intelligence (Yellow):
- What did the competitor do? (from $ARGUMENTS or web search)
- Verify the information: is this confirmed or rumor?
- Context: is this part of a pattern or a one-off?
- Assess impact (Purple):
- Does this affect our pricing? Our positioning?
- Does this threaten our pipeline or active deals?
- Which departments are affected?
- Draft response (Green, if needed):
- Counter-messaging for sales team
- Talking points for customer-facing staff
- Customer reassurance for at-risk accounts (if applicable)
- Present to Chairman: respond or ignore?
Output Format
# Competitive Alert: [Date]
## What Happened
**Competitor:** [name]
**Action:** [what they did]
**Verified:** [yes/no/partially]
**Source:** [where this information came from]
## Impact Assessment
| Department | Impact | Severity |
|-----------|--------|----------|
| Commercial | [effect on pipeline/deals] | [low/medium/high] |
| Marketing | [effect on positioning] | [low/medium/high] |
| Operations | [effect on operations] | [low/medium/high] |
## Recommended Response
**Option A: Respond**
[Specific actions: counter-messaging, price adjustment, etc.]
**Option B: Ignore**
[Why ignoring might be the right move]
**Recommendation:** [A or B with rationale]
## Decision
[ ] Respond with Option A
[ ] Ignore
[ ] Custom response: ___Rules
- Do not overreact. Most competitor moves do not require a response.
- Verify before escalating. Rumors are not actionable intelligence.
- If responding, draft is for Chairman review only. Never send directly.
- Save to
.chairman/reports/competitive-YYYY-MM-DD.md - Update marketing knowledge base with competitor intel
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.

