Install any skill in seconds. Free to start, no credit card required.
Get Started Free →m0n0x41d/h-onboard
First-setup ceremony for a project that does not yet use haft — the agent reads the repository, drafts the minimum FPF carriers (target system, enabling system, term map) from observed code/docs, and presents them to the operator for review. The operator is NOT asked to author spec files from scratch — that defeats the value of having an AI agent. Make sure to use this skill whenever the repository has no `.haft/` directory yet, when the user says "set up haft here", "onboard this project", "ini
Passed 12 of 17 test cases with the skill, and 5 of 17 without it.
and 5 more in the full report
9 fixed7 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
An operator has given clear, direct selection of a prepared profile brief. What exact command should be executed to apply this selection?
| Checked | Without skill | With skill |
|---|---|---|
| Execute haft onboard profile apply. | Missed | Passed |
The instructions your model reads when the skill loads.
Use the native Pi haft_onboard tool rather than exposing low-level profile or
memory machinery.
Contract truth: project-profile onboarding and automatic project-memory setup are V9 CONTRACT capabilities. Source, schema, skill, or local-test presence is not installed-runtime proof and does not establish Pi host parity. A readiness claim requires current EXACT-CANDIDATE EVIDENCE from P14 tied to one exact candidate; RC or release status additionally requires release authority. Pi support is experimental, and contract inclusion or evidence alone does not establish CURRENT PRODUCT status.
Start with:
{
"action": "status"
}
Follow only its closed result kind:
needs_init — run the explicitly requested haft init, reconnect when
instructed, and repeat status;needs_profile — call haft_onboard with
{ "action": "profile_prepare" };profile_review_ready — present the readable review and its exact next act;ready — only the canonical profile and structured project memory are ready.
This does not establish specification applicability, health, lifecycle, or
release readiness; use h-spec separately for specification work.haft init installs default project memory as part of initialization. Never
ask the operator to enable, defer, select, or understand a memory schema. A
legacy or partial installation reporting needs_init is repaired by rerunning
haft init, reconnecting, and repeating status.
If repository detection cannot establish the profile basis, call
profile_prepare again with the top-level readable basis and explicit
scopes. Each scope uses only scope_id, label, realization_kind, and
test cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.