pm-sdk
/pm-sdk
Implements pm-cli integrations on the published @unbrained/pm-cli SDK entrypoints and runtime contracts. Use when authoring extensions, embedding pm in another tool, building a domain on pm primitives, or keeping a wrapper aligned with command/action schema changes.
- Author
- unbraind ↗
- Repository
- pm-cli ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Implements pm-cli integrations on the published @unbrained/pm-cli SDK entrypoints and runtime contracts. Use when authoring extensions, embedding pm in another tool, building a domain on pm primitives, or keeping a wrapper aligned with command/action schema changes.
Original author description
Implements pm-cli integrations on the published @unbrained/pm-cli SDK entrypoints and runtime contracts. Use when authoring extensions, embedding pm in another tool, building a domain on pm primitives, or keeping a wrapper aligned with command/action schema changes.
How it works
- Load Order
- Entrypoints
- Non-Negotiables
- Integration Loop
- Surface Compatibility
- References
SKILL.md preview
---
name: pm-sdk
description: Implements pm-cli integrations on the published @unbrained/pm-cli SDK entrypoints and runtime contracts. Use when authoring extensions, embedding pm in another tool, building a domain on pm primitives, or keeping a wrapper aligned with command/action schema changes.
license: MIT
compatibility: Requires Node.js and access to pm contracts output for runtime parity checks.
metadata:
owner: unbrained
domain: pm-cli
scope: sdk-integration
---
# pm SDK Skill
The SDK is the implementation; the CLI and the MCP server are thin consumers of
it. Anything the CLI can do is reachable from the published surface, and an
integration should never import repository internals to get it.
## Load Order
| Tier | Load | Cost | When |
| ---- | ----------------------------------------------- | --------- | ------------------------------------- |
| 0 | This file | ~700 tok | Always. |
| 1 | `pm contracts --summary` | ~2.6k | The command/action surface. |
| 1 | `sdk/public-surface.json` | query it | Exact exported symbols and signatures.|
| 2 | `pm contracts --command <cmd> --full --json` | ~1-4k | One command's complete contract. |
| 3 | `references/*.md` below | ~0.3-1k | Procedure detail. |
| 4 | `docs/SDK.md` **by section only** | 45k whole | Never read whole; grep to a heading. |
Optional deep routing that never goes stale:
```bash
pm package install guide-shell --project
pm guide sdk
pm guide tokens --depth brief
```
## Entrypoints
Import the narrowest entrypoint that owns the capability. Startup cost is
proportional to what you import.
| Export | Capability family |
| ----------------------------------------- | -------------------------------------------------------- |
| `@unbrained/pm-cli/sdk/core` | Items, schema, profile, transactions, runtime primitives |
| `@unbrained/pm-cli/sdk/query` | List and search engines, filtering, pagination, rendering |
| `@unbrained/pm-cli/sdk/graph` | Relationship stores, traversal, analytics, remediation |
| `@unbrained/pm-cli/sdk/governance` | Validation, health, gc, transaction cleanup |
| `@unbrained/pm-cli/sdk/merge` | VCS-neutral tracker merge contracts |
| `@unbrained/pm-cli/sdk/authoring` | Extension blueprints, builders, manifests |
| `@unbrained/pm-cli/sdk/contracts` | Static command/action contracts, expected-error protocol |
| `@unbrained/pm-cli/sdk/runtime` | Embedded command execution, package runtime helpers |
| `@unbrained/pm-cli/sdk/testing` | Package and extension assertion/invocation helpers |
| `@unbrained/pm-cli/sdk` | Compatibility aggregate over every supported export |
| `@unbrained/pm-cli/sdk/public-surface.json` | Machine-readable surface snapshot shipped with the package |
| `@unbrained/pm-cli/cli` | Executable entry (`runPmCli`), not a typed library API |
Query the shipped surface instead of guessing a symbol name:
```bash
node --input-type=module -e '
import surface from "@unbrained/pm-cli/sdk/public-surface.json" with { type: "json" };
console.log(JSON.stringify(surface));
' | jq -r '.entrypoints["./sdk/graph"].symbols[:40][].name'
```
## Non-Negotiables
- Never import from `src/core/...` or any unpublished module path. The boundary
is gated and a private import fails the build.
- Never mirror an SDK type in your own package. Import it or derive it with
`typeof`; a hand-copied signature becomes immutable consumer code.
- Treat `pm contracts` output as the source of truth for flags, actions, and
availability. Snapshot it in a test so drift fails rather than surprises.
- Author identity is detected automatically. Pass an author only for a
deliberate identity override.
## Integration Loop
1. Capture the runtime surface: `pm contracts --schema-only`,
`pm contracts --runtime-only --availability-only`.
2. Map payload fields to contract keys — do not assume the CLI flag spelling
equals the SDK option key.
3. Implement against the narrowest entrypoint.
4. Add a regression test that fails when a required contract field drifts.
5. Verify the packed artifact, not just the working tree.
## Surface Compatibility
The published surface is a reviewed artifact. Additive changes are recorded;
removals and signature changes require an explicit acknowledgement with a
reason that stays in the snapshot.
```bash
pnpm sdk:surface:check
pnpm sdk:surface:update
pnpm sdk:surface:update -- --acknowledge-breaking "<release rationale>"
```
Every package export that declares a `types` path must carry a classification,
so a new public entrypoint cannot ship ungoverned.
## References
The [generated capability routing](../../../docs/generated/AGENT_CAPABILITY_ROUTING.md)
covers every declared family. Expand only the family needed, then query its
published SDK symbols and runtime contract. For MCP integrations, start with
the [current conformance matrix](../../../docs/MCP_2026_07_28_CONFORMANCE.md)
and its SDK-owned request, transport, task, subscription, Skills, and Apps
contracts; distinguish implementation evidence from exact-release acceptance.
| Need | Load | Cost |
| ------------------------------------------- | -------------------------------------------------------- | -------- |
| Step-by-step integration checklist | [Integration checklist](references/INTEGRATION_CHECKLIST.md) | ~400 tok |
| Prompt templates | [Prompts](references/PROMPTS.md) | ~200 tok |
| Which entrypoint owns which capability | [Surface map](references/SURFACE_MAP.md) | ~900 tok |
| Building a non-PM domain on pm primitives | [Domain modeling](references/DOMAIN_MODELING.md) | ~900 tok |
Files in this package (5)
- SKILL.md 6 KB
- references/DOMAIN_MODELING.md 4 KB
- references/INTEGRATION_CHECKLIST.md 1 KB
- references/PROMPTS.md 1 KB
- references/SURFACE_MAP.md 4 KB
Versions
The database has no other skills named pm-sdk.
Database snapshot: 13.11.2026 · package version 170f6bf27ed2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100sdk-wrapper-creator
Create sdk wrapper creator operations. Auto-activating skill for API Integration. Triggers on: sdk wrapper creator, sdk wrapper creator Part of the API Integration skill category. Use when working with sdk wrapper creator functionality. Trigger with phrases like "sdk wrapper… - 100build-kernel-ts-sdk
Use if building browser-automation apps on the Kernel TS SDK (@onkernel/sdk), CLI, or MCP server — browsers, pools. - 100add-command
Guide for adding new CLI commands or subcommands to todoist-cli. Use when implementing new SDK endpoints, adding subcommands to existing command groups, or extending CLI functionality. - 96fluent-cli
Use when building apps or querying data with Fluent (now-sdk) on ServiceNow. - 100add-command
Guide for adding new CLI commands or subcommands to todoist-cli. Use when implementing new SDK endpoints, adding subcommands to existing command groups, or extending CLI functionality. - 100verify-compat
Verify that generated SDK code preserves backwards compatibility with a live SDK. Use when regenerating an SDK for a language that has an existing published SDK, checking for breaking changes, regressions, or API surface drift. Also triggers for "BC check", "backwards…