AutoSkill Local Skill Manager, turn what you repeat into reusable skills — only with your approval

Manages your personal local skill files: it spots reusable habits from your sessions, drafts the skill or the diff, and writes nothing until you approve the exact text.

⚠️ Unverified listing: our automated install test could not be completed for this build (its install prompt tripped a safety filter in our test system), so we have not verified its content.

At a glance

What: Manages your personal local skill files: it spots reusable habits from your sessions, drafts the skill or the diff, and writes nothing until you approve the exact text.
Cost: Free
Needs: a Muse skills folder you can point to and confirm. Optional tooling only, never prerequisites: rg, npx/skills.sh, Python skill-creator tooling.
Install: Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@

Created by: @ECNU-ICALK

Not verified? How to check before you trust →

Install — Free View source code

⌁

Install

Copy the install package below, then paste it into Muse📌 Pinned version: commit 94c47ca

Prerequisites: a Muse skills folder you can point to and confirm. Optional tooling only, never prerequisites: rg, npx/skills.sh, Python skill-creator tooling. This fiche installs ONLY the AutoSkill Local Skill Manager SKILL.md from ECNU-ICALK. It does NOT install the AutoSkill SDK, Web UI, proxy, SkillEvo, or any Docker setup from the same repo. Do not install any of those, and do not copy a Codex skills path (such as ~/.codex/skills) never copy a Codex skills path. Install "AutoSkill Local Skill Manager, turn what you repeat into reusable skills — only with your approval" for me. It gives my agent ECNU-ICALK's local skill-file manager: after substantive sessions it runs a silent, non-blocking check for reusable preferences, rules, corrections, workflows, or failure fixes; it searches my local skills for a similar skill before creating anything; it scores candidates by evidence, recurrence, personal value, and portability; and it drafts the complete proposed skill or diff and waits for my explicit approval of that exact text before it discards, improves, merges, or creates anything. It must never write, update, delete, install, or enable a skill without my approval, never install a third-party skill without my consent, and never silently modify the autoskill manager itself. Repository: https://raw.githubusercontent.com/ECNU-ICALK/AutoSkill/94c47ca488d4ba4117d20272e66d49b9877e68cf/skills/autoskill/SKILL.md Pinned version: install the code at commit 94c47ca488d4ba4117d20272e66d49b9877e68cf exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and the optional agents/openai.yaml file, carried only if present, inert in Muse — do not rely on it) from the repository path above into a temporary folder. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This folder should contain no scripts and no secrets in code. 3. Ask me to confirm the exact Muse skills folder to use, and copy the skill there under the folder name `autoskill` only after I confirm that path. If my skills folder is unclear, ask me — do not guess a Codex path. 4. After installing, confirm the install in one line (skill name and folder path) and tell me that no skill file has been created, changed, or deleted by the install itself, and that the manager will only propose changes for my approval from now on.

After installation, ask me if I want to leave private feedback
Private for now: only the Skill Harbor team sees it. Sellers may be looped in later.

🧪 Example

You ask

Illustrative example only, not a real user's result. After this session, check whether anything here should become a reusable skill.

You get

Illustrative example only, not a real user's result. Either a short 'nothing durable enough — discarded' note, or 2–5 candidate skill titles with one-line evidence reasons plus a 'none of these' / custom-topic choice, followed — only after approval of the full draft — by a complete proposed SKILL.md or diff. Nothing is written before that approval.

Illustrative example based on this skill’s own documentation — not a real user’s result.

🔒 Security, provenance and what this touches

🔒 Security and provenance

📌 Pinned version: commit 94c47ca

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a build before installing →

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.