autoskill
Manage personal local Agent Skill files as an installable skill manager. Proactively and periodically detect reusable user-specific, team-specific, or broadly reusable skill material during or after meaningful sessions; run non-blocking extraction checks; offer candidate skill titles or accept a user-supplied topic when extraction direction is ambiguous; preserve the appropriate output language; search local and external skill ecosystems for similar skills; score candidates by evidence, recurrence, personal value, and portability; fully draft proposed skills or diffs before asking for approval
npx skills add ECNU-ICALK/AutoSkill --skill autoskill --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Local Skill File Manager ## Purpose Maintain the user's personal local skill files as a lightweight self-improving memory system. The default goal is not to produce marketplace-ready generic skills; it is to preserve reusable behavior that helps this user, this team, or this workspace in future sessions. A good candidate may encode personal workflow preferences, project conventions, style contracts, tool choices, or review gates that would not be useful to other users, as long as it is reusable for the intended owner and approved. This skill does not depend on project-specific code, servers, vector stores, databases, or storage layouts. It operates only on ordinary local skill folders: ```text <skill-root>/ <skill-name>/ SKILL.md agents/openai.yaml (optional) scripts/ (optional) references/ (optional) assets/ (optional) ``` Use this skill to decide when a session contains reusable skill material, find whether a similar skill already exists, then discard, improve, merge, or create a local skill. The model should initiate this check when signals appear; it should not wait for the user to ask. The check must stay lightweight and non-blocking unless the user explicitly asks to focus
- Purpose
- Related Skill Coordination
- Safety And Consent
- Skill Roots
- Trigger Policy
- Candidate Lifecycle
- Title Selection Gate
- Language Consistency
- Background Execution
- Confirmation Gate
- Immediate Triggers
- Scheduled Checks
- Debounce And Batching
- Experience Triage
rg --files -g 'SKILL.md' <skill-root> rg -n "<keyword|task|output-type>" <skill-root> python3 <skill-creator>/scripts/quick_validate.py <path/to/skill-folder> python3 <skill-creator>/scripts/init_skill.py <skill-name> --path <skill-root>
What does the autoskill skill do?
Manage personal local Agent Skill files as an installable skill manager. Proactively and periodically detect reusable user-specific, team-specific, or broadly reusable skill material during or after meaningful sessions; run non-blocking extraction checks; offer candidate skill titles or accept a user-supplied topic when extraction direction is ambiguous; preserve the appropriate output language; search local and external skill ecosystems for similar skills; score candidates by evidence, recurrence, personal value, and portability; fully draft proposed skills or diffs before asking for approval
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill autoskill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.