Skip to main content

Agent Skill Mastery Engine

Agent Skill Mastery Engine is a runtime-neutral implementation of the experience-to-skill evolution method described in the WikiSkill paper. One shared core owns evidence, scoring, the persistent wiki, immutable skill snapshots, strict promotion, recovery, and staging. Runtime adapters translate only measured capabilities and captured jobs.

This project was formerly named Askesis and published as the distribution askesis-agent-skill-mastery-engine; the import package and CLI were askesis.

Current status

This tree is a development candidate. It does not install itself into Hermes, Claude Code, or Codex; asme install is an explicit, user-run step that copies only Agent Skill Mastery Engine's own skill files (see Install for Claude Code). The tree has not been approved for publication or distribution. The historical Claude Revision 8 remains NEEDS REVISION; this implementation does not claim a Codex SOUND verdict.

The current Hermes adapter reports unknown trace fidelity and unsandboxed before role dispatch. Current verified public Hermes APIs do not provide an atomic provider route lock with no fallback, so this adapter refuses role dispatch before any model request. Provider-hidden reasoning cannot be relabelled as a paper-complete trace.

What works

  • Sealed, text-only train, validation, and test domains with collision-checked provenance markers generated for splits that omit them.
  • Optional named observation seed with approval, visibility checks, and rollback.
  • Prompt-only jobs bound to exact capability, provider, model, and snapshot records.
  • Real subprocess extractors and scorers with no synthetic failure score.
  • Deterministic train sampling and evidence-attested wiki changes.
  • One create, patch, or no-action skill proposal.
  • Strict validation plus fresh confirmation before promotion.
  • Accepted, rejected, confirmation-rejected, no-action, and abandoned impact records.
  • Invalid-manifest reset, intent-first recovery, staged archives, and archive readback.
  • Pre-intent dependency rehashing plus an exact output-plan hash for every workflow command.
  • Capability-bound package labels plus validated and explicitly untested staging routes. Neither route installs anything; the only install verb covers Agent Skill Mastery Engine's own skill.
  • Staging lint for version, date, concrete triggers, and inherited observation provenance.
  • A read-only observation candidate bridge that preserves Task Observer ownership and requires human review before any shared learning record is written.

Boundaries

  • Raw evidence comes from declared task and answer files, never live-session mining.
  • The core has no network client and cannot write to live runtime skill roots.
  • Task Observer, Hindsight, Second Mind, Hermes reflection, and external knowledge vaults remain separate systems. Optional observation seeds require explicit IDs, provenance, and hash-bound approval. Validated WikiSkill output can only produce a review candidate; it cannot write another system's memory or observation log.
  • Only exact OpenAI-backed provider and model allowlists are accepted for prepared jobs.
  • Candidate skills are staged only. Installation and publication are separate human approval gates. asme install never touches a staged candidate; it installs only Agent Skill Mastery Engine's own SKILL.md and companions and refuses staging and archive sources.
  • Code is MIT licensed; docs, methodology, and templates are CC BY 4.0 (selected 2026-09-01, Gate A decision A4, Option A). Projects using this work are asked, as a non-binding request, to link to manysaintvictormd.com on their project page. Publication of this tree remains a separate owner approval gate. See NOTICE.md.
  • Paper-derived method and locally authored algorithms are separated in PROVENANCE.md; it records attribution without claiming legal novelty.

Install for Claude Code

The published package carries Agent Skill Mastery Engine's own agent skill (SKILL.md, PURPOSE.md, NOTICE.md, LICENSE, and references/). Installing it is a two-step, user-run action; nothing is installed as a side effect of pip or uv.

uv tool install agent-skill-mastery-engine
asme install

asme install copies only those skill files into ~/.claude/skills/asme. Pass --target DIR for another skill directory, --dry-run to print the plan without writing, and --force to replace an existing asme skill directory. The verb refuses any --source under a staging or archive root and any staged bundle, so an evolved candidate can never be installed this way. From a development checkout, python scripts/install_claude_skill.py does the same job.

uv tool install places the asme entry point in ~/.local/bin; add that directory to PATH if asme --version is not found.

Verify:

asme --version
asme install --dry-run
ls ~/.claude/skills/asme

After a restart, Claude Code lists asme among its available skills.

Uninstall:

rm -r ~/.claude/skills/asme
uv tool uninstall agent-skill-mastery-engine

Development checkout

Use an isolated environment. This installs the Python package for development; it does not install a generated agent skill into any runtime.

python3 -m venv .venv
. .venv/bin/activate
python -m pip install -e .
python -m pytest
python scripts/stdlib_smoke.py
asme --help

The runtime package uses only the Python standard library. Pytest is needed only for the development suite.

Workflow

init
  -> seed-observations | skip-seed
  -> baseline prepare / record / ingest / finalize
  -> train prepare / record / ingest / sample
  -> apply-wiki -> proposer-context -> apply-proposal
  -> validation -> gate -> confirmation -> gate
  -> test-baseline and test-final
  -> export to staging

Every command emits JSON. status is read-only. recover replays only a recorded transaction. reset-manifest deletes invalid unconsumed evidence and the rejected capture, but preserves its .out.md for audit until a corrected capture replaces it. export and package-untested write only to the domain's staging and archive roots.

Read SKILL.md for agent-facing operation, references/integration.md for adapter rules, and references/verification/README.md before interpreting a test result as a runtime claim.

Metadata

Release files for agent-skill-mastery-engine 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agent-skill-mastery-engine 0.2.0
File Size Uploaded Provenance
agent_skill_mastery_engine-0.2.0.tar.gz 187.4 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for agent-skill-mastery-engine 0.2.0
File Interpreter ABI Platform
agent_skill_mastery_engine-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 322.2 kB

Release files / agent_skill_mastery_engine-0.2.0.tar.gz

Download URL agent_skill_mastery_engine-0.2.0.tar.gz
Size 187.4 kB
Tags Source
SHA-256 checksum
How to use checksums
29e2232f16c23313a07a7ad2ff2cddbb6dce16743bbd82e9a51c241366803e6d
BLAKE2b-256 checksum
How to use checksums
345ba85efdcafba452d2b90a94f911a18e43e888bbbdaead20e9e929828d0287
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.6

Release files / agent_skill_mastery_engine-0.2.0-py3-none-any.whl

Download URL agent_skill_mastery_engine-0.2.0-py3-none-any.whl
Size 134.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f271795a375c7587a9460f30993d3f1125275e5163855a6e87ec72c2a06f09e3
BLAKE2b-256 checksum
How to use checksums
63f7d02105c1d1efd8afc5b1435d49901dab1e401acf4910d8c3d9fe56f12f95
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.6

Security for agent-skill-mastery-engine 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page