Skill Discovery

Run this campaign before using discovered local skills or corpus material as task context. Keep project-local instructions under their own authorized project route; they are not corpus search results.

Frame the task and source scope

1. Reduce the request to the task and outcome, topic, platform, material form, constraints or failure modes, and useful names, aliases, and tags. State which sources are in scope, the effective namespace, any physical collection filter, and what evidence would make the selected material sufficient for this task.
2. Keep semantic subject navigation separate from physical collection filters. Use tree --view subjects|collections to find navigation nodes. Pass a returned node ID to browse; pass a physical collection name to --category. For a corpus-only search, use --namespace skills-db; select skills or _repos only when that source scope is part of the request.

Check: The task brief names the needed outcome, search facets, source scope, and a task-specific sufficiency condition before results are judged.

Start browse and query together

Launch a browse track and an initial query together. Keep both active, share useful nodes and terms across them, and let each continue while the other runs. When either returns a candidate that plausibly addresses a framed task facet within the authorized scope, load it immediately using the next section before waiting for query five or treating query-count or overlap requirements as complete. Keep the other track and remaining useful queries active during that load. A first hit never closes the campaign.

Use tree and browse to map relevant subject or collection branches and paginate descriptor results where needed: