agentleFS
stoa-platformstoa-platform/stoa/.claude/skills/competitive-watch/SKILL.md

competitive-watch

Skill9 starsChanged 7 months agoApache-2.0View on GitHub

Veille concurrentielle IA Factory — sources, digest format, audit scoring.

The file

Files
SKILL.md

Competitive Watch Skill

Veille concurrentielle integree a l'IA Factory STOA. 3 niveaux d'execution.

Sources (par priorite)

1. Boris Cherny (@bcherny) — Createur Claude Code

2. Anthropic Engineering Blog

3. Claude Code Docs & Releases

4. Concurrence directe

OutilChangelogFocus
Cursorhttps://cursor.com/changelogComposer, multi-file, AI rules
Windsurf (Codeium)https://codeium.com/blogCascade, flows
Aiderhttps://aider.chat/HISTORY.htmlModes, benchmarks
OpenAI Codex CLIhttps://github.com/openai/codexSandbox, autonomie
Amazon Q Developerhttps://aws.amazon.com/q/developer/AWS integration
Google Jules / Gemini CLIhttps://developers.googleblog.comWorkspace integration

5. Communaute

  • Reddit r/ClaudeAI : top posts semaine
  • Reddit r/cursor : top posts semaine
  • Hacker News : recherche "Claude Code" ou "AI coding"
  • Dev.to / Medium : tags "claude-code", "ai-coding-assistant"

6. MCP Ecosystem

Architecture L1 — Mode Accumulation

L1 fonctionne en 2 phases (collect + digest) avec accumulation JSONL:

watch-collect.sh (2x/jour)           watch-digest.sh (lundi)
  Sources → JSONL append      →     Dedup + tri + format digest
  .claude/watch/signals-YYYY-WNN.jsonl

Phase 1: Collect (watch-collect.sh)

  • Cadence: 2x/jour (08:00 + 18:00 CET)
  • Append-only: chaque signal = 1 ligne JSONL
  • Dedup a l'ecriture: source+title (case-insensitive)
  • Fichier par semaine ISO: signals-2026-W09.jsonl
  • 6 sources: Anthropic blog, npm, Reddit, HN, Cursor, Aider

Phase 2: Digest (watch-digest.sh)

  • Cadence: lundi 08:00 CET
  • Lit les signaux de la semaine courante
  • Deduplique (source+title), trie par score
  • Produit le digest formate (voir format ci-dessous)
  • Optionnel: poste sur Slack via $SLACK_WEBHOOK

Format JSONL (un signal)

{"ts":"2026-02-24T08:00:00+00:00","source":"reddit","title":"...","url":"...","score":142,"meta":{}}

L'ancien one-shot (competitive-watch.sh) reste disponible pour affichage rapide en CLI.

Format du Digest (L1 — hebdomadaire)

:telescope: VEILLE IA FACTORY — Semaine YYYY-WNN

:loudspeaker: BREAKING (action requise)
- [changement majeur qui impacte notre setup]

:new: NOUVEAUTES
- Claude Code vX.X.X : [features notables]
- Boris tip : [resume si nouveau thread]

:crossed_swords: CONCURRENCE
- Cursor : [mouvement notable]
- [autre concurrent] : [mouvement notable]

:speech_balloon: COMMUNAUTE (top signaux)
- [Reddit/HN posts classes par score]

:bulb: PATTERNS A TESTER
- [pattern vu dans la communaute qu'on n'utilise pas encore]

:bar_chart: NOTRE SCORE
- Setup actuel : XX/100 (dernier audit)

:dart: ACTION ITEMS
- [ ] [action concrete si necessaire]

Execution

NiveauCadenceDeclencheurOutil
L1 Collect2x/jour (8h + 18h CET)cron / launchd / n8nscripts/ai-ops/watch-collect.sh
L1 DigestHebdo (lundi 8h CET)cron / launchd / n8nscripts/ai-ops/watch-digest.sh
L1 One-shotManuel (CLI)Utilisateurscripts/ai-ops/competitive-watch.sh
L2 AuditMensuel (1er du mois 8h UTC)GHA cron.github/workflows/monthly-ia-factory-audit.yml
L3 BenchmarkTrimestrielManuel/benchmark-competitors slash command

Setup cron/launchd/n8n: voir scripts/ai-ops/CRON-SETUP.md

Usage

User: /competitive-watch digest     → lance le digest de la semaine courante
User: /competitive-watch collect    → lance une collecte manuelle
User: /competitive-watch audit      → affiche le dernier score audit
User: /competitive-watch benchmark  → lance le benchmark trimestriel complet

Regles

  • Objectivite : chercher ce que les concurrents font MIEUX, pas moins bien
  • Factuel : toujours citer la source et la date
  • Actionnable : chaque observation doit mener a une action concrete ou un "no action needed"
  • Pas de veille passive : si rien de notable, le digest le dit explicitement

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.