Tool reference · practitioner
compose_capability
Compose a new capability into a repository
The harvest lane: read what a repository can already do, then offer codeless capability nominations that fuse those affordances with owned SHPBL primitive capabilities — DREAM, EVOLUTION, MEMORY, DEFENSE, BRAIN and the rest of the canonical forty, plus the S-Tier artifacts. Each nomination names host evidence, proposed capability bodies, Capability Contract slots, a test plan, and honest limits. It contains no implementation; approved materialization belongs to `harvest_repo`. Free calls return host affordances, then stop before library correlation; nominations require a Practitioner key (7-day free trial).
Call it
curl -X POST https://shpbl.com/api/public/v1/tools/compose_capability \
-H 'content-type: application/json' \
-H 'authorization: Bearer shpbl_mcp_…' \
-d '{}'Same handler over MCP. The free lane needs no key; a Practitioner key is what keeps a run.
Required arguments
repo
A GitHub repository: `owner/repo` or a URL.
Optional arguments
key
Your SHPBL Practitioner subscription key (shpbl_mcp_…). Optional if your client sends it as the `Authorization: Bearer …` request header.
github_token
Optional GitHub token (Contents: read) for a private repository.
include
Optional path filter — only paths containing this text are read for affordances.
grants
How many codeless capability nominations to return, 1 to 200. Ranked by measured fit and capability standing.
per_affordance
How many nominations one affordance may produce, 1 to 200. Raise it to see alternative leads for the same host capability.
pages
How many source pages to read for affordance evidence, 1 to 12 (about 90,000 characters each). More pages means more of the tree is read; the grants are cut from whatever was read.