Install
$ agentstack add skill-itaywol-adeptability-adept-self-improve ✓ 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.
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
Self-improve: turn lessons into skills
adept skills are portable memory. A lesson written as a skill is loaded by every harness on every future session — not lost when this context ends. When you learn something durable, capture it instead of forgetting it.
When to capture
Capture when the lesson is durable and reusable, not one-off:
- The user corrects you ("we always use X, not Y", "don't touch Z").
- A fix or pattern generalizes beyond the file you're in.
- You discover a project convention the code doesn't make obvious (a build gate, a
naming rule, a required pre-PR step).
- You catch yourself thinking "I'll remember that for next time." — you won't; the skill will.
Don't capture: secrets, one-shot facts, anything already obvious from the code or existing skills. Improve an existing skill before adding a near-duplicate (adept skill list).
The loop
adept skill list # does a skill already cover this? edit it if so
adept skill add --edit # else scaffold a new one
# write a triggering description + a tight, harness-neutral body
adept sync # render to every enabled harness
adept status && adept diff # confirm it landed clean
Then tell the user, in one line, what you captured and where — they own the memory, so let them veto it. Commit the new skill with their normal review.
What makes a captured lesson good
- Description = trigger. Front-load when it applies so a future agent loads it at the
right moment. See [[authoring-adept-skills]] for crafting the description and activation.
- Atomic. One lesson per skill. If it needs "and also…", it's two skills.
- Reason, not just rule. "Use sentinel errors so callers can
errors.Is" beats "use
sentinel errors" — the why survives refactors the rule wouldn't.
Confirm before you persist
Capturing is an outward, durable act: it changes how every future session behaves. Surface what you're about to write and let the user confirm — don't silently rewrite the project's shared memory. See [[using-adept]] for the surrounding CLI.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: itaywol
- Source: itaywol/adeptability
- License: MIT
- Homepage: https://pkg.go.dev/github.com/itaywol/adeptability
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.