mirror of
https://github.com/katanemo/plano.git
synced 2026-04-25 00:36:34 +02:00
Some checks are pending
CI / pre-commit (push) Waiting to run
CI / plano-tools-tests (push) Waiting to run
CI / native-smoke-test (push) Waiting to run
CI / docker-build (push) Waiting to run
CI / validate-config (push) Waiting to run
CI / security-scan (push) Blocked by required conditions
CI / test-prompt-gateway (push) Blocked by required conditions
CI / test-model-alias-routing (push) Blocked by required conditions
CI / test-responses-api-with-state (push) Blocked by required conditions
CI / e2e-plano-tests (3.10) (push) Blocked by required conditions
CI / e2e-plano-tests (3.11) (push) Blocked by required conditions
CI / e2e-plano-tests (3.12) (push) Blocked by required conditions
CI / e2e-plano-tests (3.13) (push) Blocked by required conditions
CI / e2e-plano-tests (3.14) (push) Blocked by required conditions
CI / e2e-demo-preference (push) Blocked by required conditions
CI / e2e-demo-currency (push) Blocked by required conditions
Publish docker image (latest) / build-arm64 (push) Waiting to run
Publish docker image (latest) / build-amd64 (push) Waiting to run
Publish docker image (latest) / create-manifest (push) Blocked by required conditions
Build and Deploy Documentation / build (push) Waiting to run
* feat: add initial documentation for Plano Agent Skills * feat: readme with examples * feat: add detailed skills documentation and examples for Plano --------- Co-authored-by: Adil Hafeez <adil.hafeez@gmail.com>
990 B
990 B
| name | description | license | metadata | ||||
|---|---|---|---|---|---|---|---|
| plano-advanced-patterns | Design advanced Plano architectures. Use for multi-listener systems, prompt target schema quality, and layered orchestration patterns. | Apache-2.0 |
|
Plano Advanced Patterns
Use this skill for higher-order architecture decisions once fundamentals are stable.
When To Use
- "Design a multi-listener Plano architecture"
- "Improve prompt target schema precision"
- "Combine model, prompt, and agent listeners"
- "Refine advanced routing/function-calling behavior"
Apply These Rules
advanced-multi-listeneradvanced-prompt-targets
Execution Checklist
- Use multiple listeners only when interfaces are truly distinct.
- Keep provider/routing definitions shared and consistent.
- Define prompt target parameters with strict, explicit schemas.
- Minimize ambiguity that causes malformed tool calls.
- Provide migration-safe recommendations and test scenarios.