Skip to content

Behavior and dependency reference

This page describes the published skill instructions. The quickstart covers first use.

The workflow establishes the requested outcome, designs instructions and conditional references, builds one working artifact, and exercises relevant behavior. It can begin with a new workflow, existing draft, focused correction, or review-only request.

The author consults source methods when they help resolve the current decision. Those methods do not become separate mandatory workflows.

SourceContribution
Anthropic Skill CreatorIntent, examples, reusable resources, and evaluation design.
Matt Pocock’s Writing for AgentsTriggers, information hierarchy, conditional pointers, and completion criteria.
Poteto’s Automate MeHistory and preference evidence when the task requires it.
Zach PromptingContract preservation, instruction conflicts, and draft review.
Codex Skill CreatorNative packaging, metadata, structural validation, and proportionate scaffolding.
Poteto runtime supportRelative runtime-mapping references used by the locked methods.

Source authors retain their licenses and authorship. The bundled Codex snapshot retains its Apache-2.0 license. Inclusion does not imply endorsement.

InputPurpose
Workflow or existing artifactDefines behavior to create, improve, or review.
Intended tasks and exclusionsSets triggering conditions and scope.
Target runtime and destinationDetermines packaging and where files belong.
Protected requirements and authorizationPreserves approval rules and action limits.
Examples and acceptance checksMakes success observable.

The result includes the artifact path, enabled behavior, consequential source contributions or disagreements, a dependency receipt, actual checks, and remaining gaps. Review-only requests return findings without editing the target.

Delivery reports use validated for tested behavior, awaiting-evals for behavior awaiting trials, no-change-needed when no change is required, or blocked with a specific dependency gap. Comparative quality claims require comparative evidence.

Missing or modified required sources fail preflight. Independent preparation can continue, but a similarly named global skill cannot silently replace a locked source.

Creating a skill does not authorize its future business actions. Authoring a deployment workflow does not authorize deploying a product. A task-specific permission or exception retains its original scope.

Claude-specific evaluation scripts need that runtime and its dependencies. Codex can use supported bounded agents and must identify unavailable measurements. Structural checks, authoring trials, runtime discovery, and downstream execution are separate claims.

File or directoryContract
package.jsonDeclared sources, commands, and private installation destination.
package-lock.jsonPinned dependency installer.
skills-lock.jsonSource commits and content integrity.
.runtime/skills/Private restored source copies.
.sources/codex-creator/Bundled Codex snapshot and original license.
.sources/origins.jsonBundled-source provenance.
references/Composition boundaries, dependency operations, and validation choices.
evals/Synthetic fixtures and historical evaluation evidence.

The preflight JSON receipt contains checkedAt, wrapper, lockSha256, manager, status, and skills. It proves installed content matches the lock, not that upstream has no newer version or that behavior is correct.

Run these in the installed sams-skill-creator directory:

CommandEffect
npm ci --ignore-scriptsRestores the pinned installer.
npm run skills:installRestores sources using the frozen skill lock.
npm run preflight --silentChecks integrity and prints a JSON receipt.
npm testRuns dependency-integrity tests.
npm run skills:listLists declared dependencies.
npm run skills:outdated --silentChecks freshness without changing pins. Unavailable checks remain unknown.
npm run skills:updateResolves upstream updates and changes the lock and installed sources.

Normal runs keep verified pins. A requested refresh preserves the previous source set, checks updates, reviews changed guidance, and freezes the accepted set before authoring.

skills:update does not automatically replace the bundled Codex snapshot from the host. That refresh requires inspection, source replacement, provenance recording, and relocking. See dependency operations for the full sequence and rollback procedure.

Freshness applies at the recorded check time. No scheduled update is installed.