name	resource-discovery-config
description	pi-crew resource and configuration discovery workflow.
origin	pi-crew
triggers	["discover agents","find teams","config override","resource discovery","skill loading"]

resource-discovery-config

Use this skill for pi-crew resource/config work.

Source patterns distilled

Pi resource loader: source/pi/packages/coding-agent/src/core/resource-loader.ts, extension resources_discover hook
pi-crew discovery: src/agents/discover-agents.ts, src/teams/discover-teams.ts, src/workflows/discover-workflows.ts
Config: src/config/config.ts, src/schema/config-schema.ts, schema.json, docs/resource-formats.md

Rules

Respect discovery precedence: project resources should override user/builtin where supported.
Keep built-in resource formats stable and documented.
Project config (.pi/pi-crew.json) must be sanitized: do not allow dangerous user-only settings such as agent override injection if project trust is lower.
Resource paths exposed through Pi hooks must point to package-root resources after build; verify __dirname resolution carefully.
Avoid dynamic inline imports; keep discovery synchronous or async according to call-site expectations.
Validate config with schema and provide actionable errors.
When adding new config fields, update defaults, schema, docs, tests, and examples together.

Enforcement — Resource Discovery Config Gate

Before adding config or changing resource discovery, verify:

Discovery precedence respected (project > user > builtin)
Config schema validated with actionable errors on invalid input
Dangerous user-only settings blocked in lower-trust contexts
Resource paths resolved correctly (package-root not src/skills after build)
New config fields have defaults, schema, docs, tests, and examples

If ANY answer is NO → Stop. Fix config/discovery issues before proceeding.

Anti-patterns

Resolving package skills to src/skills instead of package-root skills after publishing.
Letting project-local config inject arbitrary global agent overrides.
Introducing precedence ambiguity between project/user/builtin resources.
Changing resource file syntax without migration notes.

Verification

cd pi-crew
npx tsc --noEmit
node --experimental-strip-types --test test/unit/config-schema-validation.test.ts test/unit/config.test.ts test/unit/extension-api-surface.test.ts test/unit/agent-override-skills.test.ts
npm test
npm pack --dry-run

Más de este repositorio

mismo repositorio

iterative-audit

baphuongna/pi-crew

Iterative multi-round codebase audit with diminishing-returns detection. Run 5-20+ rounds, each focusing on one specific area. Built from 19 rounds of dogfooding pi-crew on itself.

2026-06-3038

widget-rendering

baphuongna/pi-crew

Pi TUI crew widget data sources, display priority, and rendering performance.

2026-06-3038

orchestration

baphuongna/pi-crew

Multi-phase orchestration for planners and executors.

2026-06-2238

council

baphuongna/pi-crew

Spawn 3 adversarial subagents (Skeptic, Pragmatist, Critic) to evaluate a decision, architecture choice, or plan. Anti-anchoring: each role receives ONLY the question, not conversation history. Aggregates votes into consensus recommendation with dissent tracking. Use when facing critical decisions, architecture choices, security tradeoffs, or plan reviews where single-perspective analysis is insufficient.

2026-06-0438

async-worker-recovery

baphuongna/pi-crew

Background worker, heartbeat, stale-run, crash-recovery, and deadletter workflow. Use when debugging stuck/dead workers or changing async run reliability.

2026-06-0338

child-pi-spawning

baphuongna/pi-crew

Child Pi worker spawning, lifecycle callbacks, and failure modes.

2026-06-0338

resource-discovery-config

Use this skill for pi-crew resource/config work.

Source patterns distilled

Pi resource loader: source/pi/packages/coding-agent/src/core/resource-loader.ts, extension resources_discover hook

pi-crew discovery: src/agents/discover-agents.ts, src/teams/discover-teams.ts, src/workflows/discover-workflows.ts

Config: src/config/config.ts, src/schema/config-schema.ts, schema.json, docs/resource-formats.md

Rules

Respect discovery precedence: project resources should override user/builtin where supported.

Keep built-in resource formats stable and documented.

Project config (.pi/pi-crew.json) must be sanitized: do not allow dangerous user-only settings such as agent override injection if project trust is lower.

Resource paths exposed through Pi hooks must point to package-root resources after build; verify __dirname resolution carefully.

Avoid dynamic inline imports; keep discovery synchronous or async according to call-site expectations.

Validate config with schema and provide actionable errors.

When adding new config fields, update defaults, schema, docs, tests, and examples together.

Enforcement — Resource Discovery Config Gate

Before adding config or changing resource discovery, verify:

Discovery precedence respected (project > user > builtin)

Config schema validated with actionable errors on invalid input

Dangerous user-only settings blocked in lower-trust contexts

Resource paths resolved correctly (package-root not src/skills after build)

New config fields have defaults, schema, docs, tests, and examples

If ANY answer is NO → Stop. Fix config/discovery issues before proceeding.

Anti-patterns

Resolving package skills to src/skills instead of package-root skills after publishing.

Letting project-local config inject arbitrary global agent overrides.

Introducing precedence ambiguity between project/user/builtin resources.

Changing resource file syntax without migration notes.

Verification

cd pi-crew npx tsc --noEmit node --experimental-strip-types --test test/unit/config-schema-validation.test.ts test/unit/config.test.ts test/unit/extension-api-surface.test.ts test/unit/agent-override-skills.test.ts npm test npm pack --dry-run