session-health
Skill1 starsChanged 45 days agoNo licenceView on GitHub
Session Health: assess the current AI coding tool session — context compaction/condensation ratio, message count, context occupation cost, work nature, recoverability (git/handoff/runtime), and token economics — to judge continue vs new-session. Reads tool session storage read-only. Use when the user mentions context compaction, starting a new session, high context overhead, or long-session continuation (e.g. "go" / "keep going"). NOT for: auditing skill descriptions, full-codebase architecture analysis, or product-doc set audits.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- flonat/flonat-researchtheir own version, first seen Nov 3, 2026
- Cal-Starfur/claude-skillstheir own version, first seen Jun 21, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- flonat/flonat-research★ 150same name
- Cal-Starfur/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository93 other files it gives its agents.
- accessibility-auditorSkill
- agent-dispatchSkill
- api-contract-validatorSkill
- architecture-patternsSkill
- audit-itemSkill
- autonomous-investigationSkill
- battle-card-builderSkill
- cicd-pipelineSkill
- codebase-designSkill
- code-reviewSkill
- company-intelSkill
- competitive-analysis-processSkill
- competitive-intel-watchSkill
- competitive-research-snapshotSkill
- config-scanSkill
- core-rulesSkill
- coverage-matrixSkill
- customer-journey-mapSkill
- ddd-aggregatesSkill
- ddd-context-mapSkill
- ddd-contextsSkill
- ddd-discoverSkill
- ddd-domain-interactionsSkill
- ddd-model-reviewSkill
- ddd-openspec-bridgeSkill
- ddd-qa-chainSkill
- ddd-scopeSkill
- ddd-subdomainsSkill
- ddd-tactical-reviewSkill
- decision-logSkill
- deep-codebase-analysisSkill
- delegated-researchSkill
- dependency-scanSkill
- discovery-interview-prepSkill
- electron-best-practicesSkill
- env-checkSkill
- event-stormingSkill
- executing-plansSkill
- experiment-handoffSkill
- frontend-designSkill
- git-workflowSkill
- grill-meSkill
- intelligence-collection-disciplinesSkill
- jobs-to-be-doneSkill
- k6-performanceSkill
- llm-gateway-opsSkill
- marketing-copywritingSkill
- market-landscape-scanSkill
- perf-checkSkill
- pipeline-0to1Skill
- pixel-perfectSkill
- plan-grillingSkill
- playwright-best-practicesSkill
- positioning-statementSkill
- positioning-workshopSkill
- prd-developmentSkill
- prd-driven-dddSkill
- press-releaseSkill
- problem-handlingSkill
- problem-statementSkill
- The first 60 shown.
The file
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.