Capability-tiered instruction digest

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

Teaching host H reads project instruction files but cannot discover slash skills or call suite-specific tools. Offer guidance it can follow rather than implying a full workflow is installed. Digest v1 covers inspecting existing code, evidence-based status and user scope; 2 KiB is this example’s byte budget.

Mechanism

Verify actual instruction locations, discovery and tool capability, then choose the full suite or instruction tier. For limited hosts generate a short versioned behavioral/reuse digest with a route to full capabilities and an instruction-only label. Offer it for user-controlled integration without overwriting existing rules; regenerate and check versions after upgrades.

Bad example

After pasting a digest into H, claim the suite installed, invoke unavailable review/QA/deploy commands and overwrite existing project instructions.

Good example

Confirm H reads instructions but lacks suite tools. Offer digest v1: inspect existing implementations before adding; support status claims with actual checks; stay within user scope. Keep the teaching 2-KiB budget, show its version and explicitly state that review/QA/deployment tools and complete workflows are absent. Identify a loaded location for user integration, preserving existing rules. Use a separately supported install path for full capabilities.

Why the change matters

Capability tiers prevent text from being mistaken for installation. Portable stable principles plus explicit gaps/versioning tell recipients which guidance is usable and which work needs another environment.

Observable expectation

Inspect version, UTF-8 bytes, loaded location and capability labels. H can follow guidance but cannot call absent commands. Preserve existing instructions and an upgrade integration step.

Unloaded generated files, overwritten rules or unsupported full-suite claims fail.

Limits

Byte budgets do not measure session tokens, and digests provide no evaluation/capability guarantee. Frozen host lists/versions need current verification. No installation or user-instruction edit occurs here.