SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillssource-command-cowork-veille

source-command-cowork-veille

Office & productivity

View repository

Updated 10-15 21:42

About this skill

source-command-cowork-veille

Use this skill when the user asks to run the migrated source command cowork-veille.

Command Template

Codex Cowork Product Watch

Search the web for what's new in the Codex desktop app, compare with the local CHANGELOG, and identify undocumented gaps.

Full pipeline:

/cowork:veille          →  Découvre les gaps, propose des entrées CHANGELOG
  ↓ (review manuelle)
/cowork:update-releases →  Sync CHANGELOG → YAML → TS

Step 1: Parse Arguments

  • --deep : use perplexity_deep_research instead of perplexity_search (slower, more exhaustive)
  • --since <YYYY-MM-DD> : only consider announcements after this date; if absent, use the date of the last CHANGELOG entry
  • --sources <all|blog|reddit|press> : filter sources (default: all)

Step 2: Read the current state of the CHANGELOG

Read /Users/florianbruniaux/Sites/perso/Codex-cowork-guide/CHANGELOG.md.

Extract:

  1. Baseline date : date of the first ## [X.Y.Z] - YYYY-MM-DD (most recent entry) → used as automatic --since if not provided
  2. Documented features : flat list of all bullet items from all sections (Added, Changed, Fixed) of all versioned versions. Ignore versioning metadata.
  3. Section [Unreleased] : note its content if non-empty.

Display in debug:

📋 CHANGELOG baseline: YYYY-MM-DD (vX.Y.Z)
📦 Features documentées: N items
📝 [Unreleased]: X items

Step 3: Web searches (in parallel)

Launch the 4 queries in parallel via perplexity_search (or perplexity_deep_research if --deep).

⚠️ Do NOT use "Cowork" in the queries — internal term, not used publicly. ⚠️ Filter out results mentioning "terminal", "CLI", "npm", "Codex", "Codex" — that's another product.

# Query Target
1 Anthropic Codex desktop app new features 2026 Official announcements
2 Codex.ai desktop update changelog site:anthropic.com OR site:docs.anthropic.com Anthropic blog/docs
3 Codex desktop app features reddit 2026 Community discoveries
4 "Codex" desktop "new feature" OR "update" OR "plugin" OR "connector" 2026 Tech press

If --sources blog : queries 1 + 2 only. If --sources reddit : query 3 only. If --sources press : query 4 only. If --sources all or absent: all 4.

Apply the filter --since to ignore features announced before the baseline date.

Step 4: Fetch reference pages

Do WebFetch on these 2 URLs in parallel:

  • https://docs.anthropic.com/en/docs/Codex-ai/Codex-desktop — official desktop docs
  • https://www.anthropic.com/news — Anthropic blog (scan for desktop/features mentions)

Silently skip if 404, timeout, or redirect to an irrelevant page. Do not block on fetch errors.

Step 5: Compare and score

For each feature/claim found in the search results and fetched pages:

  1. Extract the concrete claim : plugin X, capability Y, platform Z — something testable and precise
  2. Fuzzy match against the list of documented features extracted in Step 2:
    • Exact or near-exact match → ALREADY DOCUMENTED, skip
    • Partial or ambiguous match → UNCLEAR, note
    • No match → NEW GAP, keep
  3. Score confidence based on the source:
    • HIGH : anthropic.com, docs.anthropic.com, official announcement
    • MEDIUM : reputable tech press (TechCrunch, The Verge, Ars Technica, etc.)
    • LOW : Reddit, forums, unverified individual posts

Deduplicate identical claims found in multiple sources (keep the most reliable source).

Step 6: Display the Gap Report

=== Codex Cowork Product Watch ===
Baseline: YYYY-MM-DD (vX.Y.Z)
Sources: 4 queries + 2 anchor pages
Filtre: features après YYYY-MM-DD

--- NOUVEAUX GAPS (pas dans CHANGELOG) ---

[HIGH] <Feature name> (source officielle, <date>)
  Source: <URL>
  Résumé: <1-2 phrases factuelles>
  → Catégorie suggérée: Added | Changed | Fixed

[MEDIUM] <Feature name> (<publication>, <date>)
  Source: <URL>
  Résumé: <1-2 phrases>
  → Catégorie suggérée: Added

[LOW] <Feature name> (Reddit, non confirmé)
  Source: <URL>
  → Vérification nécessaire avant documentation

--- DÉJÀ DOCUMENTÉ (<N> features matchées) ---
<liste condensée ou "Tout semble à jour.">

--- PAS CLAIR (<N> résultats ambigus) ---
<items avec incertitude, ex: "Mention de X mais contexte flou">

---
Total gaps HIGH+MEDIUM : N
Total gaps LOW (non confirmés) : N

If no gap found: display "✅ No gap detected. CHANGELOG up to date as of YYYY-MM-DD." and finish.

Step 7: Draft CHANGELOG (optional)

If HIGH or MEDIUM gaps were found, ask:

"Draft CHANGELOG entries for the confirmed gaps (HIGH + MEDIUM)? (y/n)"

If n or no response → finish here.

If y :

  1. Generate the entries in Keep-a-Changelog format for each HIGH and MEDIUM gap
  2. Group them under ### Added, ### Changed, ### Fixed according to the suggested category
  3. Add them to the section ## [Unreleased] of the CHANGELOG (below the line ## [Unreleased])
  4. If the section [Unreleased] is empty: add the necessary subsections
  5. If it already contains items: add the new items to the existing subsections or create the missing subsections

Format of the generated entries:

## [Unreleased]

### Added
- <Feature X> : <description factuelle, 1 ligne, basée sur la source>
- <Feature Y> : <description>

Display confirmation:

✅ <N> entrées ajoutées dans [Unreleased]
   → Relire CHANGELOG.md avant de couper une version
   → Puis : /cowork:update-releases pour sync YAML + landing

LOW gaps are NOT added automatically — tell the user to check them manually if they wish.