check-anthropic
Skill16 starsChanged 7 months agoMITView on GitHub
Fetches the Claude Code GitHub releases page and official docs to find new hooks, CLAUDE.md features, and skills API changes. Cross-references against what this project currently uses and rates each gap for relevance. Run every few weeks or after a major Claude Code release. Triggers on /check-anthropic or \"check for new Anthropic features\" or \"what's new in Claude Code\".
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- actSkill
- security-checkSkill
- environment-checkSkill
- run-verificationSkill
- refactorSkill
- debug-session-archivedSkill
- generate-guardsSkill
- code-reviewerSkill
- code-reviewSkill
- debug-sessionSkill
- end-sessionSkill
- evolve-checkSkill
- evolveSkill
- fix-bugSkill
- forgetSkill
- frontend-designSkill
- guardSkill
- kit-healthSkill
- learnSkill
- map-codebaseSkill
- modeSkill
- parallel-prototypesSkill
- planSkill
- powershell-safeSkill
- product-riskSkill
- progress-reportSkill
- prototype-hypothesisSkill
- recallSkill
- refactoring-uiSkill
- scan-codebaseSkill
- scan-conventionsSkill
- search-firstSkill
- search-memorySkill
- shadow-codeSkill
- skill-creatorSkill
- smart-resumeSkill
- start-sessionSkill
- strategic-compactSkill
- tourSkill
- ux-heuristicsSkill
- verification-loopSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Read each page and extract:
- Very specific: line 34
Read .claude/settings.json (project-level hooks)
- Very specific: line 35
Read ~/.claude/settings.json (global hooks, if exists)
- Distinctive: line 37
Read CLAUDE.md — note any @imports and rules/ files in use
- Distinctive: line 103
Run every 4-6 weeks, or after any Claude Code release announcement
- Very specific: line 105
If a new hook is rated High, create a plan with Plan [hook name integration] before implementing
- Distinctive: line 106
Update the known hook list in Step 3 if new official hooks are found
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Skill: check-anthropic
Trigger: /check-anthropic or "check for new Anthropic features" or "what's new in Claude Code"
Description: Fetches the Claude Code GitHub releases page and official docs to find new hooks, CLAUDE.md features, and skills API changes. Cross-references against what this project currently uses and rates each gap for relevance. Run every few weeks or after a major Claude Code release.
Allowed Tools: WebFetch, Read, Glob
Steps
1. Fetch what's new
Fetch these three pages in parallel:
https://github.com/anthropics/claude-code/releases— recent releases, changelogshttps://code.claude.com/docs/en/hooks— full current hook event listhttps://code.claude.com/docs/en/memory— CLAUDE.md + @imports + rules/ features
Read each page and extract:
- Any new hook event names not previously known
- Any new CLAUDE.md syntax or frontmatter fields
- Any new skills API capabilities
- Any new settings.json options
2. Read what this project currently uses
- Read
.claude/settings.json(project-level hooks) - Read
~/.claude/settings.json(global hooks, if exists) - Glob
.claude/skills/*/SKILL.md— list all skills, count them - Read
CLAUDE.md— note any @imports and rules/ files in use
Extract: all hook event names currently wired.
3. Cross-reference against known full hook list
The full official hook list as of last verification (25 events):
SessionStart, UserPromptSubmit, PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure, Notification, SubagentStart, SubagentStop, TaskCreated, TaskCompleted, Stop, StopFailure, TeammateIdle, InstructionsLoaded, ConfigChange, CwdChanged, FileChanged, WorktreeCreate, WorktreeRemove, PreCompact, PostCompact, Elicitation, ElicitationResult, SessionEnd
Compare: hooks in use vs full list → identify unused hooks. Also check: any hooks on the fetched docs page that are NOT in the list above → those are new.
4. Rate each gap
For every unused hook (and any new features found), rate relevance:
| Rating | Meaning |
| High | Directly serves memory, learning, or automation goals — should evaluate now |
| Medium | Could help in specific scenarios — worth knowing about |
| Low | Niche use case unlikely to apply here |
Guidance for rating hooks:
PostCompact— High: re-inject memory context after compaction firesSessionEnd— High: complement to Stop, fires on clean exitFileChanged— Medium: more granular drift detection than PostToolUse Edit|WriteStopFailure— Medium: capture state when Claude errors outSubagentStop— Low unless this project uses subagentsTaskCompleted— Medium: hook into task completion for auto-loggingTeammateIdle— Low: multi-user setups onlyConfigChange— Low: fires when settings change
5. Report
Output in this format:
## Claude Code Feature Check — [date]
### Releases scanned
[list any releases found with key changes]
### Hook coverage
Currently using: N / 24 hooks
[list hooks in use]
### High-priority gaps
[hook name] — [one line: what it does + why it's relevant here]
### Medium gaps
[hook name] — [one line]
### New features found (not in baseline)
[anything on the docs page not in the known list above]
### CLAUDE.md / Skills API
[any new syntax, frontmatter fields, or skills features found]
### Recommendation
[1-2 sentences: what to investigate next]Notes
- Run every 4-6 weeks, or after any Claude Code release announcement
- Pairs well with
/evolve— run check-anthropic first, then evolve to implement anything rated High - If a new hook is rated High, create a plan with
Plan [hook name integration]before implementing - Update the known hook list in Step 3 if new official hooks are found
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.

