Menu

Individual skill

action-skill-contracts

Author deterministic skills for operations that change state or invoke external tools

.copilot/skills/action-skill-contracts/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 authoring or revising a skill that can mutate files, state, repositories, or
external systems. Informational reference skills need not carry operational ceremony.

## Patterns

- Start with an explicit `## SCOPE`: activation conditions, allowed targets, and exclusions.
- Provide an ordered, deterministic workflow. State required inputs, the intended side effect, and
  the exact validation after each consequential operation.
- Define STOP conditions for missing prerequisites, ambiguous scope, failed verification, and
  unavailable tools. A failed precondition must not look like success.
- Point to a current canonical implementation or workflow when a procedure depends on repository
  behavior; do not copy volatile values into prose.