# Cc Updates

> >

- **Type:** Skill
- **Install:** `agentstack add skill-almax000-claude-skills-cc-updates`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [almax000](https://agentstack.voostack.com/s/almax000)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [almax000](https://github.com/almax000)
- **Source:** https://github.com/almax000/claude-skills/tree/main/cc-updates

## Install

```sh
agentstack add skill-almax000-claude-skills-cc-updates
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# CC Updates — Anthropic 生态更新情报

Research the latest Claude Code + Anthropic-ecosystem updates and generate
project-specific actionable recommendations. The skill is **surface-aware**:
findings are grouped by where they live (CC CLI vs API vs Labs products vs
community) so the user sees the full Anthropic stack, not just the CLI.

## When to Use

Invoke this skill when the user wants to:
- Know what's new in **Claude Code** (CLI, hooks, MCP, skills, memory)
- Know what's new in the **Anthropic API** (new models, pricing, caching,
  tool use, SDK changes, breaking changes)
- Know what's new in **Anthropic Labs & products** (Design, Cowork, Desktop
  app, Chrome extension, Routines, Computer Use, Skills SDK)
- Get actionable advice on adopting new features for their current project
- Audit their CC config against latest best practices
- Stay current with community-discovered workflows and patterns

## Input Parsing

Parse the invocation for time range:
- `/cc-updates` → default 14 days
- `/cc-updates 7d` → 7 days
- `/cc-updates 30d` → 30 days
- Only `d` (days) suffix is supported. Unrecognized formats fall back to 14.

Extract `TIME_RANGE_DAYS` from the invocation. Run these via Bash:
- `TODAY=$(date +%Y-%m-%d)`
- `CURRENT_YEAR=$(date +%Y)`
- `CUTOFF_DATE=$(date -v-{TIME_RANGE_DAYS}d +%Y-%m-%d)` (macOS)
- Linux fallback: `CUTOFF_DATE=$(date -d "-{TIME_RANGE_DAYS} days" +%Y-%m-%d)`

**Template token injection (critical):** after computing these values,
substitute `{TIME_RANGE_DAYS}`, `{CUTOFF_DATE}`, `{TODAY}`, and
`{CURRENT_YEAR}` into the Agent A and Agent B prompt text **before** spawning
the Task tool. Do not pass the raw template with unfilled `{...}` placeholders
— the researcher will fail or misinterpret. Pass the fully resolved text.

## Surface Taxonomy (important)

Every update returned by Agent A MUST be tagged with exactly one **surface**:

| Surface | Emoji | What belongs here |
|---------|-------|-------------------|
| `cc-core` | 🟣 | Claude Code CLI releases, hooks, skills, MCP, memory, slash commands, plan/auto mode, subagents, permissions, sandboxing |
| `api-models` | 🟢 | New Claude models (Opus/Sonnet/Haiku), pricing, prompt caching TTL, tool use extensions, SDK changes (Python/TS), API breaking changes, task budgets, citations, **Computer Use API** |
| `labs-products` | 🟡 | Anthropic Labs launches (Claude Design), Claude Desktop app, Chrome/Browser extension, Claude on the Web, Routines, Cowork, Skills SDK (non-CC), mobile apps |
| `community` | 🔵 | Reddit/blog/YouTube workflow tips, CLAUDE.md best practices, multi-agent patterns, notable public use cases |

Rule: if unsure between two surfaces, pick the one closest to **where a
developer would configure it**. Examples:
- **Opus 4.7** → `api-models` (model is API-side, even though CC ships an
  `xhigh` flag for it)
- **Routines** → `labs-products` (runs in Anthropic cloud, configured via
  claude.ai/code — not in local CC CLI)
- **PreCompact hook** → `cc-core` (configured in local `.claude/settings.json`)
- **Computer Use** → default `api-models` (the API); only classify as
  `labs-products` if a new consumer-app surface ships (e.g. a standalone
  desktop automation product)
- **Skills SDK** → `labs-products` when it's the non-CC platform SDK;
  `cc-core` when the release is CC CLI's skill system

## Execution: Two Parallel Agents

Immediately spawn Agent A (researcher) and Agent B (explorer) in **parallel**
using the Task tool. Do NOT wait for one to finish before starting the other.
Remember to resolve all `{TIME_RANGE_DAYS}`, `{CUTOFF_DATE}`, `{TODAY}`,
`{CURRENT_YEAR}` placeholders in the prompts below before spawning.

---

### Agent A Prompt — researcher (model: opus, max effort)

```
You are a researcher agent. Your task: find every notable update across the
ENTIRE Anthropic ecosystem (not only Claude Code) from the last
{TIME_RANGE_DAYS} days (since {CUTOFF_DATE}). Today is {TODAY}.

Use WebSearch and WebFetch aggressively. Do NOT summarize or truncate — return
full details including code examples.

## Budget & Stopping Rules

- **Wall-time budget**: 25 minutes max. If approaching the budget, stop
  launching new searches and synthesize what you have.
- **Impact shortcut**: if you already have ≥ 15 HIGH-impact updates across
  surfaces, stop further searches and compile results.
- **Quality over completeness**: 10 well-documented updates > 25 shallow ones.

## Required Searches — Execute (subject to budget)

### Block 1 — Claude Code Core (surface: cc-core)
1. WebSearch: "Claude Code changelog {CURRENT_YEAR}"
2. WebSearch: "Anthropic Claude Code release notes {CURRENT_YEAR}"
3. WebFetch: https://github.com/anthropics/claude-code/releases
4. WebFetch: https://github.com/anthropics/claude-code/raw/refs/heads/main/CHANGELOG.md
5. WebSearch: "Claude Code MCP server {CURRENT_YEAR} update"
6. WebSearch: "Claude Code hooks preToolUse postToolUse PreCompact {CURRENT_YEAR}"
7. WebSearch: "Claude Code skills SKILL.md {CURRENT_YEAR}"
8. WebSearch: "Claude Code memory auto memory {CURRENT_YEAR}"
9. WebSearch: "Claude Code sub-agents agent teams {CURRENT_YEAR}"
10. WebSearch: "Claude Code slash commands {CURRENT_YEAR}"
11. WebSearch: "Claude Code permissions auto mode {CURRENT_YEAR}"
12. WebSearch: "Claude Code breaking changes deprecated {CURRENT_YEAR}"
13. WebFetch: https://code.claude.com/docs/en/whats-new
14. WebFetch: https://code.claude.com/docs/en/changelog

### Block 2 — Anthropic API & Models (surface: api-models)
15. WebSearch: "Anthropic API new model release {CURRENT_YEAR}"
16. WebSearch: "Claude Opus Sonnet Haiku release {CURRENT_YEAR}"
17. WebSearch: "Anthropic API pricing change {CURRENT_YEAR}"
18. WebSearch: "Anthropic prompt caching TTL {CURRENT_YEAR}"
19. WebSearch: "Anthropic SDK python typescript update {CURRENT_YEAR}"
20. WebSearch: "Anthropic API tool use breaking change {CURRENT_YEAR}"
21. WebSearch: "Anthropic task budgets beta {CURRENT_YEAR}"
22. WebSearch: "Anthropic model deprecation retirement {CURRENT_YEAR}"
23. WebSearch: "Anthropic computer use API {CURRENT_YEAR}"
24. WebFetch: https://www.anthropic.com/news
25. WebFetch: https://docs.claude.com/en/release-notes
26. WebFetch: https://docs.claude.com/en/release-notes/api

### Block 3 — Labs & Products (surface: labs-products)
27. WebSearch: "Claude Design Anthropic Labs {CURRENT_YEAR}"
28. WebSearch: "Claude Cowork release {CURRENT_YEAR}"
29. WebSearch: "Claude Desktop app redesign {CURRENT_YEAR}"
30. WebSearch: "Claude Chrome extension browser agent {CURRENT_YEAR}"
31. WebSearch: "Claude Code Routines cloud automation {CURRENT_YEAR}"
32. WebSearch: "Anthropic Skills SDK agent {CURRENT_YEAR}"
33. WebSearch: "Claude computer use consumer app {CURRENT_YEAR}"
34. WebSearch: "Claude mobile app iOS Android {CURRENT_YEAR}"
35. WebFetch: https://www.anthropic.com/news — **DEDUPE**: this URL was
    already fetched in Block 2 (#24). Do NOT re-fetch. Reuse the content from
    Block 2 and tag each post by surface: model/pricing/API → `api-models`;
    new consumer/dev product → `labs-products`; CC-specific → `cc-core`.

### Block 4 — Community & Best Practices (surface: community)
36. WebSearch: "Claude Code tips workflow reddit {CURRENT_YEAR}"
37. WebSearch: "best CLAUDE.md examples github {CURRENT_YEAR}"
38. WebSearch: "Claude Code productivity multi-agent {CURRENT_YEAR}"
39. WebSearch: "Claude Code youtube tutorial {CURRENT_YEAR}"
40. WebSearch: "site:reddit.com claude code new feature {CURRENT_YEAR}"
41. WebSearch: "Anthropic engineering blog {CURRENT_YEAR}"

For each result that looks relevant: use WebFetch to get the FULL page content.
Do not skip pages due to length.

## Retry Policy
- Max 3 attempts per URL. After 3 failures, mark as "blocked" and move on.
- If a site is blocked, do NOT retry with different user-agents or workarounds.
  Record it in SOURCES_CHECKED and continue.

## Output Format

Return this exact structure:

### UPDATES_FOUND

For each update:
- **title**: short name
- **surface**: one of [cc-core, api-models, labs-products, community]
- **source**: URL
- **date**: publication date or "unknown"
- **category**: one of [feature, bug-fix, workflow, config, MCP, agent,
  memory, performance, breaking-change, model-release, pricing, community-tip]
- **impact**: one of [high, medium, low]
- **cross_surface_hint**: OPTIONAL — if this update interacts with another
  surface (e.g. new API model that also ships a CC effort flag), note it here
  so the synthesis step can link them. Otherwise: null.
- **description**: FULL description, do not truncate. Include code examples
  if source has them.
- **raw_quote**: exact quote from source

### SOURCES_CHECKED

List all URLs you searched/fetched with: url | status
(found_content / no_relevant_content / blocked)

### SEARCH_COVERAGE

Rate per surface independently:
- cc-core: [excellent / good / limited]
- api-models: [excellent / good / limited]
- labs-products: [excellent / good / limited]
- community: [excellent / good / limited]

Then give an overall one-line rating with the weakest link called out.
```

---

### Agent B Prompt — explorer (model: default)

```
You are a project context explorer. Scan the current working directory and
Claude config.

Thoroughness level: medium

## What to Read

1. Run `pwd` to get current directory
2. Read `./CLAUDE.md` if it exists (project-level config)
3. Read `~/.claude/CLAUDE.md` (global config)
4. Read ALL files in `~/.claude/rules/` directory
5. List `~/.claude/skills/` directory
6. List `~/.claude/commands/` directory
7. Run `ls -la` in current directory
8. Detect tech stack:
   - Read `package.json` if exists
   - Read `pyproject.toml` or `requirements.txt` if exists
   - Read `Cargo.toml` if exists
   - Read `go.mod` if exists
9. Read `.claude/settings.json` if it exists
10. List `~/.claude/projects/` to understand project history
11. If project has `.claude/rules/` and/or `.claude/skills/`, list and sample
    them — these often contain domain-specific conventions the report must
    respect

## Additional Signals to Capture (for cross-surface matching)

The synthesis step will try to match Anthropic-ecosystem updates to project
needs. Capture these signals explicitly so matching works:

### Product / Code Signals
- **Does the project consume the Anthropic API directly?**
  (grep for `@anthropic-ai/sdk`, `anthropic` in package.json /
  pyproject.toml, or `ANTHROPIC_API_KEY` in `.env.example`)
- **Does the project have a design system or branding rules?**
  (look for `.claude/rules/branding.md`, `rules/design-system.md`,
  `tokens.css`, Storybook, Figma links in README) — relevant for Claude Design
- **Does the project use VLM / image / OCR?**
  (grep for `vlm`, `vision`, `ocr`, image-related dependencies) —
  relevant for vision-capacity upgrades
- **Does the project have scheduled / background work?**
  (cron, GitHub Actions schedule:, dispatcher, polling loops) —
  relevant for Routines
- **Does the project involve native desktop or GUI automation?** —
  relevant for Computer Use

### CC Infrastructure Signals (used by Layer 3 to ground recommendations)
- **hooks_count**: count `.sh`/`.py`/`.js` files in `.claude/hooks/`
  (project-level) and `~/.claude/hooks/` (global). Relevant when new hook
  events (PreCompact, PermissionDenied, etc.) ship.
- **skills_count_project**: count directories in `.claude/skills/`
- **skills_count_global**: count directories in `~/.claude/skills/`
- **has_memory_system**: is
  `~/.claude/projects//memory/MEMORY.md` present? If yes, note
  its line count (>200 triggers the CLAUDE.md-length best practice).
- **has_agent_teams_setting**: grep
  `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` in settings — relevant for
  Agent Teams features.

## Output Format

### PROJECT_CONTEXT
- cwd: current directory path
- project_name: inferred from directory name or package.json
- is_project_dir: true/false (false if running from ~)
- tech_stack: list of detected technologies
- has_project_claude_md: true/false
- project_claude_md_summary: key rules/workflows (if exists)
- uses_anthropic_api_directly: true/false/unknown (+ evidence)
- has_design_system: true/false/unknown (+ evidence)
- uses_vision_or_ocr: true/false/unknown (+ evidence)
- has_scheduled_work: true/false/unknown (+ evidence)
- involves_native_gui_automation: true/false/unknown (+ evidence)

### CC_INFRASTRUCTURE_SIGNALS
- hooks_count: N (project) + M (global)
- skills_count_project: N
- skills_count_global: M
- has_memory_system: true/false (+ line count of MEMORY.md if exists)
- has_agent_teams_setting: true/false

### GLOBAL_CC_CONFIG
- rules_files: list with brief summary of each
- skills_installed: list
- commands_installed: list
- notable_config: non-default or interesting settings

### PROJECT_CC_CONFIG
- project_rules_files: list with brief summary (if .claude/rules/ exists)
- project_skills: list (if .claude/skills/ exists)
- project_hooks: list (if .claude/hooks/ exists)
- project_settings: summary of .claude/settings.json (if exists)

### GAPS_AND_PATTERNS
- Patterns that seem manually maintained (could be automated)
- Config areas that look thin or missing
- Rules that look potentially outdated
- Skills that might overlap with new CC features
```

---

## Synthesis: Three-Layer Output

After BOTH agents complete, produce the three-layer report. Actively
cross-reference — do NOT just concatenate.

### Cross-reference rules

1. For each update from Agent A: check Agent B context — is it relevant,
   irrelevant, or already handled?
2. For each gap from Agent B: does any Agent A update directly address it?
3. Elevate impact rating if the project has infrastructure to immediately
   benefit (e.g. project already has PreCompact-adjacent hook infra → any
   new hook event becomes high-impact for this project).
4. **Cross-surface synergy**: if a model change (api-models) + a CC feature
   (cc-core) compound (e.g. Opus 4.7 xhigh + Claude Code xhigh flag), surface
   them together in Layer 2 as a single recommendation, not as two entries.

   **Synthesis-time rescan (do this even if `cross_surface_hint` is null):**
   before finalizing Layer 2, scan Layer 1 for these common synergy patterns
   and bundle matches:
   - Model release (`api-models`) × CC effort/flag (`cc-core`)
   - API change (`api-models`) × SDK update (`api-models`)
   - Labs product (`labs-products`) × CC feature that enables handoff
     (`cc-core`) — e.g. Claude Design handoff + CC design-system skill
   - New MCP capability (`cc-core`) × SDK/API addition (`api-models`)

5. **Labs products relevance gate**: Claude Design relevance is proportional
   to `has_design_system`. Routines relevance is proportional to
   `has_scheduled_work`. Computer Use product relevance is proportional to
   `involves_native_gui_automation`.

   If the signal is false AND there's no adjacent workflow that could use
   the feature, mark relevance "暂不相关" and keep the Layer 1 entry but
   skip Layer 2/3 for it.

   **Operational definition of "adjacent workflow":** a concrete file in
   the project (cron job, GitHub Actions `schedule:`, polling composable,
   scheduled skill, background worker, GUI test) that serves the same
   purpose the Labs feature would replace. If Agent B's report doesn't
   name such a file, assume "no adjacent workflow" and skip Layer 2/3.
   Always add a one-line Layer 1 note: "项目暂无对应使用场景，如有需要
   再评估".

### Output Header

```
═══════════════════════════════════════════════════════════
Anthropic 生态更新情报  |  过去 {TIME_RANGE_DAYS} 天  |  {TODAY}
项目: {PROJECT_NAME}  |  目录: {CWD}
搜索覆盖度:
  🟣 cc-core: {coverage}   🟢 api-models: {coverage}
  🟡 labs-products: {coverage}   🔵 community: {coverage}
═══════════════════════════════════════════════════════════
```

---

## Layer 1 — What's New / 更新概览（按 Surface 分组）

**Grouping rule**: emit four subsections in this fixed order (skip a
subsection only if Agent A returned zero updates for that surface AND
coverage rating was "limited" — otherwise include even empty sec

…

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [almax000](https://github.com/almax000)
- **Source:** [almax000/claude-skills](https://github.com/almax000/claude-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** yes
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-almax000-claude-skills-cc-updates
- Seller: https://agentstack.voostack.com/s/almax000
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.