Agent Skills
Reusable agent workflows distributed as @sebastienelet/agent-skills. The derived index
lists the 39 skills and their purposes. Resources, attribution notices and historical evaluations
travel with their skill; historical observations do not qualify this package or current agent versions.
Prepared from the tracked sources at dotfiles revision
89307efa.
Registry installation, provenance and Claude, Codex or Cursor activation require independent verification. Dotfiles keeps its current sources and consumers until publication, independent installation and rollback have been verified.
Acquisition and selection
After publication, acquire an exact version in a durable consumer-owned directory:
bun install --exact --ignore-scripts @sebastienelet/agent-skills@<version>
The package does not install tools, hooks or agent configuration. The consumer selects individual
skills and projects their directories into the chosen host's native discovery location. Preserve
the whole skill directory, refuse divergent destinations, and keep project and user scope distinct.
Do not install the whole collection indiscriminately or expose the same slug twice. Maintain source
in this repository's skills/, never through a deployed link or node_modules.
Use implement for changes, bug-fix for repairs and plan for planning, with orchestrate retaining
the task across stages. issue-start, issue-workflow, issue-spec and issue-sync keep tracker
(Linear or GitHub Issues) separate from forge (GitHub or Bitbucket): Linear + GitHub and
Linear + Bitbucket are both supported paths. Probe only the selected providers.
claude-developer retains the manual handoff. Independent review is optional unless requested or
already required; code-review handles review alone, code-review-fix local corrections and
pr-fix authorized open-PR repair. No agent or Codex integration is mandatory for ordinary development.
User instructions supply preferences,
including note naming and the default Obsidian corpus. This package supplies
no personal instructions, corpus, agent/model selection, credentials or service configuration.
Optional companions
These separately owned capabilities are not bundled or installed automatically. Each is listed with its exact package version; availability and their consumer paths still require qualification:
| Capability | Package | Consumer |
|---|---|---|
| Context handoff | @sebastienelet/[email protected] | Workflows requesting handoff |
| Proof integrity | @sebastienelet/[email protected] | Reviews changing verification mechanisms |
| Scenario/evidence validation | @sebastienelet/[email protected] | Collection evaluation maintenance |
| Herdr issue launch | @sebastienelet/[email protected] | Explicit Herdr issue workflows |
Evaluation CI remains pending the qualified
agent-experiments interface; its validator is not copied here. Each skill declares its own other
prerequisites, including forge access or third-party tools. issue-sync remains a manual tracker reconciliation
workflow; it neither calls nor replaces the retired Bitbucket–Linear synchronization CLI.
output-discipline-hook belongs to output-discipline and requires Bun. Its
integration reference describes the opt-in and
manual host configuration. The generic auditor configuration travels with
design-claim-audit; model and effort remain host choices.
Local contribution and release
Use Bun 1.4.3, bun install --frozen-lockfile, bun test, bun run typecheck and
bun run format:check. Use skill-manager for changes and regenerate skills/README.md twice.
bun pm pack --dry-run inspects the native package contents. A local tarball is preparation evidence,
not a registry or agent activation check. Supported hosts are Claude Code, Codex and Cursor according
to each skill's declared scope; the collection makes no uniform platform or activation guarantee.
The manual publish.yml workflow publishes to npm with OIDC and provenance, after repository and
trusted-publisher setup, then creates the GitHub release v<version>. Its owner/repository/workflow
identity must match npm's trusted publisher configuration.
No npm token fallback is configured. Dispatch publication from main after configuring the trusted
publisher. Local checks do not establish registry installation, provenance or host activation.
The root MIT license covers original contributions. Skill-local licenses and attributions retain their own applicability, including Matt Pocock, Ayoub Ghriss and the visual explanation references.