Menu

Individual skill

content-scope

Keep Squad documentation focused on shipped behavior and clearly bounded integrations

.copilot/skills/content-scope/SKILL.md

Read pinned source

Source commit 12fbcb5ac4b4075abb5d2ce743f4ba1be77e0200

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 3, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,340
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Context

Use this skill when deciding whether proposed documentation, examples, or external material
belongs in Squad documentation.

## Patterns

- Apply the “Squad ships it” test: keep behavior, configuration, and integration contracts that
  Squad ships; exclude external infrastructure that users build around Squad.
- When documenting a platform feature used with Squad, identify it as a platform integration
  rather than implying Squad implements the platform feature.
- Preserve reusable product guidance while linking to external examples, articles, or deployment
  material instead of importing their operational specifics into product documentation.