Evolve Claude Md
Update CLAUDE.md with durable knowledge from the current session. Use at the end of a working session to promote new findings, renamed variables, refined definitions, or corrected assumptions into the permanent project record.
Install
$ agentstack add skill-dgilford-ai-science-toolkit-evolve-claude-md ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-dgilford-ai-science-toolkit-evolve-claude-md) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Review the current session and update CLAUDE.md with anything durable that it doesn't yet know.
What belongs in CLAUDE.md
Promote only knowledge that is:
- Permanent — true beyond this session (not current task state)
- Project-level — relevant to anyone working in this repo
- Non-obvious — not derivable from reading the code directly
Good candidates: renamed or new variables, corrected definitions, newly understood warn patterns, confirmed pipeline behavior, resolved ambiguities about data schema, architectural decisions with non-obvious rationale.
Good: Pipeline requires --baseline to be passed explicitly; there is no default. — permanent code behavior that would surprise any future developer.
Bad: Dataset coverage is 1981-09-01 through 2026-05-16 (16,329 zarrs). — describes the current data artifact being processed, not the codebase. Belongs in HANDOFF.md.
The test: if removing this fact would cause a future developer to misunderstand how the pipeline works, it belongs here. If it describes the data being processed this session, it belongs in the handoff.
Do not add: session-specific state, task progress, anything already in CLAUDE.md, speculative findings, or things that belong in HANDOFF.md.
Steps
- Read
CLAUDE.mdin full. - Scan the session for new knowledge: check git diff, recently modified files, and conversation context.
- Identify specific additions or corrections — be precise about what changed and why.
- If nothing meaningful warrants an update, say so explicitly and stop.
- Otherwise, make targeted edits to
CLAUDE.md. Do not rewrite sections that don't need changing. - Briefly summarize what was added or corrected and why.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dgilford
- Source: dgilford/ai-science-toolkit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.