Skip to content
Back to skills

Competing

ASecurity

Improve systematically by analyzing losses, studying winners, and tracking progress against rivals in any competitive domain.

  • 17 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 6, 2026
documentation

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned September 6, 2026

npx -y skills add clawic/skills --skill competing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Competing?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Competing
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/clawic-competing/badge)](https://www.skillsdirectory.com/skills/clawic-competing)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: Competing
slug: competing
version: 1.0.0
description: Improve systematically by analyzing losses, studying winners, and tracking progress against rivals in any competitive domain.
homepage: https://clawic.com/skills/competing
metadata:
  clawdbot:
    emoji: πŸ†
    displayName: Competing
---

## Core Framework

Competition is a learning accelerator. Every loss contains the lesson that wins don't.

1. **Analyze the Loss** β€” Don't just lose, understand WHY
2. **Study the Winner** β€” What did they do that you didn't?
3. **Track the Delta** β€” Measure the gap, watch it shrink
4. **Iterate** β€” Apply lessons, compete again, repeat

---

## The Post-Loss Protocol

After any competitive loss, extract value:

| Question | Purpose |
|----------|---------|
| At what moment did the outcome shift? | Find the decision point |
| What did they do that I didn't? | Identify the winning move |
| What would I do differently? | Formulate the lesson |
| Is this a pattern? | Check history for repeats |

Don't rationalize. Don't blame externals. Extract the actionable insight.

---

## Tracking (What to Measure)

Create a tracking folder in the user's workspace:

```
~/Clawic/data/competing/
β”œβ”€β”€ domains/           # Per-domain tracking
β”œβ”€β”€ rivals.md          # Opponent profiles
β”œβ”€β”€ log.md             # Win/loss log with lessons
└── progress.md        # Metrics over time
```

For each domain, track:
- Win/loss record with dates
- Specific losses analyzed (who, why, lesson)
- Patterns identified (recurring weaknesses)
- Progress metrics (are lessons translating to wins?)

---

## Rival Intelligence

Know your competition:
- **Profile rivals** β€” Their strengths, weaknesses, tendencies
- **Monitor changes** β€” When they improve or change strategy
- **Find their edge** β€” What specifically makes them beat you?
- **Study up** β€” Find examples of them losing, analyze what worked

---

## Quick Reference

| Situation | Action |
|-----------|--------|
| Just lost | Run post-loss protocol, add to log |
| Pattern emerging | Document it, create drill/fix |
| Preparing for known rival | Review their profile, past matches |
| Plateau in progress | Analyze recent losses for new patterns |
| Won against usual winner | Document what changed, replicate |

---

## Load Reference

| Need | File |
|------|------|
| Domain-specific strategies | `domains.md` |
| Deep loss analysis framework | `analysis.md` |
| Progress tracking templates | `tracking.md` |
| Feedback loop mechanics | `feedback.md` |

Files in this skill

  • SKILL.md2.5 KB
  • _meta.json170 B
  • analysis.md2.2 KB
  • domains.md2.4 KB
  • feedback.md2.4 KB
  • tracking.md2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…