Borrowing it
Nothing to install: this file belongs to anam-org/metaxy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/anam-org/metaxy/main/.claude/skills/claude-improve-config/SKILL.mdgit clone --depth 1 https://github.com/anam-org/metaxyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/anam-org/metaxy/claude-improve-config)<a href="https://agentmods.dev/skills/anam-org/metaxy/claude-improve-config"><img src="https://agentmods.dev/badge/skills/anam-org/metaxy/claude-improve-config/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/anam-org/metaxy/claude-improve-config"><img src="https://agentmods.dev/badge/skills/anam-org/metaxy/claude-improve-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00034 | $0.00892 |
| Opus 5 | $0.00017 | $0.00446 |
| Sonnet 5 | $0.00007 | $0.00178 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
claude-improve-config scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Config Self-Improvement
Analyze the current session for errors, mistakes, or inefficiencies and propose improvements to the .claude configuration to prevent similar issues in the future.
When to Use
- After a session with significant mistakes or rework
- When you notice patterns that could be prevented with better configuration
- When explicitly requested via
/claude-improve-config - Automatically triggered by the
SessionEndhook
Self-Reflection Process
1. Analyze the Session
Review the conversation for:
- Repeated mistakes: Same error made multiple times
- Misunderstandings: User had to correct Claude's interpretation
- Inefficient workflows: Better approaches discovered late in the session
- Tool misuse: Wrong tool for the job, excessive tool calls
- Missing context: Information that would have helped if in CLAUDE.md
- Ignored instructions: Existing CLAUDE.md rules that were violated
2. Categorize Issues
Rate severity:
- Critical: Caused significant rework or user frustration
- Moderate: Caused delays or minor corrections needed
- Minor: Slight inefficiency but didn't impact outcome
Only propose changes for critical or moderate issues.
3. Propose Configuration Changes
Changes can include:
CLAUDE.md Updates:
- New guardrails or constraints
- Clarified existing instructions
- Project-specific patterns to follow
New Hooks:
- PreToolUse hooks to prevent specific mistakes
- PostToolUse hooks to validate outputs
- Stop hooks to enforce checks before completion
New Skills:
- Reusable knowledge for recurring tasks
- Best practices for specific domains
4. Format the Proposal
Present proposals clearly:
## Session Reflection
### Issues Identified
1. **[Critical/Moderate]** Brief description of the issue
- What happened: ...
- Why it happened: ...
- Impact: ...
### Proposed Changes
#### Change 1: [Type - CLAUDE.md/Hook/Skill]
**Rationale:** Why this change prevents the issue
**Implementation:**
[Show the exact changes to make]
#### Change 2: ...
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 142 lines · 34 tokens per session scan A ec040894d091
claude-improve-config is a skill published in the GitHub repository anam-org/metaxy (120 stars, last pushed 20d ago), licensed Apache-2.0. It adds 34 tokens to every session and 892 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other skills, from other repositories
data-data-catalog
Use this skill when asked about data catalog, DataHub, Amundsen, Apache Atlas, OpenMetadata, metadata management, data discovery, business glossary, data lineage, data ownership, or column-level lineage. This skill enforces: metadata ingestion pipelines, column-level lineage tracking, business glossary management…
data-pipelines
Apply Data Pipelines Pocket Reference practices (James Densmore). Covers Infrastructure (Ch 1-2: warehouses, lakes, cloud), Patterns (Ch 3: ETL, ELT, CDC), DB Ingestion (Ch 4: MySQL, PostgreSQL, MongoDB, full/incremental), File Ingestion (Ch 5: CSV, JSON, cloud storage), API Ingestion (Ch 6: REST, pagination, rate…
akf-trust-metadata
The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing.
playwright-validation
Use when validating UI changes in a branch require Playwright E2E testing. Reviews branch changes, validates UI with Playwright MCP, and adds missing test cases.
pr-checklist
Use when opening or finalizing a GitHub PR for OpenMetadata. Walks through the repo PR template — linked issue, high-level design (for big PRs), unit/integration/Playwright tests + coverage, UI screen recording, and manual test steps — then drafts a fully-filled PR body and (optionally) creates the PR.
ui-checkstyle
Run the exact ESLint + Prettier + organize-imports sequence that CI's UI Checkstyle workflow runs — on just the files the PR changed — and fail the task if any file ends up with a diff. Invoke after authoring or modifying any .ts, .tsx, .js, .jsx, or .json file under openmetadata-ui/src/main/resources/ui/src/…