Menu

Individual skill

ccf-common

0upvotes

Required shared preflight for every CCFA skill after ccf-humanization: apply routing, scope, prerequisites, evidence rules, handoffs, and artifact contracts. Also maintain and audit these shared rules. Research deliverables remain with their specialist owners.

ccf-common/SKILL.md

Read pinned source

Source commit 91ca9e2801698466f934b557a75ce46db8ba46b5

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 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,482
Repository last updated
Oct 31, 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

# CCF Common

## Required Shared Preflight

First apply [ccf-humanization](../ccf-humanization/SKILL.md), then this entry, before every CCFA specialist. Bootstrap once; reuse applicable active rules across contributors and restore missing or changed rules. Discovery metadata or a named preflight is not proof that its instructions were read. Ordinary work needs no startup report, intake form, state file, or maintenance workflow.

Resolve the requested result, scope/permissions, integrating owner, and reusable or missing prerequisites. Current user instructions override defaults. Preserve plan-only, review-only, supplied-evidence-only, no-browsing, no-new-files, exact-output, and session-denylist constraints. Necessary local steps and specialist contributions remain authorized within the requested deliverable; do not re-ask solely because ownership changes.

Use one integrating owner, bring in the specialist needed to resolve a material gap, and verify affected results before finalizing. Reuse valid evidence rather than repeating intake, searches, full reports, or model calls. Do not skip groundwork to save tokens. A specialist remains responsible for its research deliverable; Common supplies shared controls.

## Preferences And Continuity

Resolve optional preferences once with `python <ccf-common>/scripts/preferences.py resolve`, adding `--project <established-root>` when known. Reuse the compact result at handoffs. Missing files mean defaults with no write or question. Read [preferences.md](references/preferences.md) only for a relevant trigger, configuration change, resolver error, or unavailable Python. Preferences govern optional enhancements and marked draft modes, not preflights, accuracy, requested scope, model selection, or host permissions.
Back to top