ccf-common
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.
Install / Use
npx skills add mikubaka88/CCFA-Skills --skill ccf-commonInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Tags
Our assessment of ccf-common
ccf-common scores 90/100 on our quality scale, 428th of 1,155 Content & Media skills we index (top 38%).
Its SKILL.md is 7.1 KB long, well organised into 9 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 2,825 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so ccf-common is actively maintained.
- Our last check on 2026-10-30 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
ccf-common compared with similar skills
All 4 of these similar skills score higher than ccf-common; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| ccf-common (this skill)by mikubaka88 | 90 | 2.8k | 2mo ago | SKILL.md |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install ccf-common?
- Run
npx skills add mikubaka88/CCFA-Skills --skill ccf-common. The install tabs above show the steps for each supported agent. - Which AI agents does ccf-common work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is ccf-common safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is ccf-common still maintained?
- The repository was last updated about 2 months ago, so ccf-common is actively maintained.
Skill content
View source on GitHubname: ccf-common description: "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." metadata: ccf_skill_controls: handoff_question_mode: partial respect_session_denylists: true protect_idea_scope_in_writing: true private_material_safety: moderate shared_controls: references/
CCF Common
Family File Contract
Before writing, resolve the canonical output and one stable working directory per task/artifact. Reuse explicit or established task paths; otherwise use project-root ccfa-workfiles/<purpose>/<artifact-id>/, with source/, assets/, cache/, and build/ only as needed. Update current files in place; do not scatter intermediates or create iteration copies. Preserve inputs and required evidence; clean only verified disposable files created by this task. Use UTF-8 text I/O and check Chinese text after saving or rendering. For file work, apply artifact-contracts.md and reuse the same paths across skill transitions.
Collaboration Contract
Before applying these shared controls, activate ccf-humanization unless its baseline is already active. Apply this entry once, then continue specialist work; do not recursively re-enter either preflight. Reuse applicable rules across contributors.
Keep one integrating owner and actively use other skills to resolve missing prerequisites or check material findings. Reuse applicable evidence; do not skip necessary groundwork to save tokens. Before finalizing, integrate contributions and verify affected results. Follow the conditional cooperation routes; avoid unrelated stages and duplicate reports.
Core Rule
This is the shared control module activated before every CCFA specialist, after ccf-humanization. It sets the task's scope, integrating owner, relevant prerequisites, evidence boundaries, and file paths while specialist skills produce research deliverables. Applying these controls does not run the maintenance workflow or require a governance report.
Invocation Controls
CCFA Handoff Mode: PARTIAL (Recommended). Follow metadata.ccf_skill_controls.handoff_question_mode and references/handoff-modes.md. On a direct invocation, ensure Humanization's baseline has been read before applying these controls. Do not recursively restart either preflight. Reuse applicable rules across contributors and read only the shared references needed for the current decision.
Family Preflight
Resolve the requested result, scope/permissions, integrating owner, and missing or reusable prerequisites. Use references/routing.md for collaboration and references/handoff-modes.md for transitions. Apply evidence/privacy rules when handling sources or private material, artifact rules before file work, and review standards when assessing. Reuse loaded rules and known paths; create no intake form or state file merely to activate this skill. Continue the specialist task once the applicable controls are established. Reserve the maintenance workflow below for actual family-maintenance requests.
Shared Controls
Load only the references needed for the current preflight decision or maintenance task:
references/routing.md: Use to resolve which CCFA skill owns a request and to avoid trigger overlap.references/task-modes.md: Use for exploratory/quick/standard depth, authorization-aware continuation, selective context, host-supported parallel work, and GPT-6 adaptation.references/review-output-standards.md: Use to keep numeric scoring, multi-reviewer panels, score-change conditions, and visible output quality consistent.references/handoff-modes.md: Use to interpretmetadata.ccf_skill_controls.handoff_question_mode.references/privacy-and-evidence.md: Use when handling manuscripts, reviews, rebuttals, private drafts, literature searches, or evidence claims.references/source-registry.yaml: Use as the shared source inventory for venue rules, review methods, exemplar records, and research-workflow references.references/ccf-a-venue-map.md: Use when a non-writing skill needs venue-family mapping without depending onccf-paper-writer.references/skill-trigger-registry.yaml: Use as the canonical trigger registry; compare descriptions and agent prompts with the same ownership boundaries.references/artifact-contracts.md: Use whenever a skill creates or revises files; it defines ownership, canonical paths, minimal intermediate-file generation, overwrite-in-place defaults, task-scoped cleanup, and required retained history.references/ccfa-yaml-contract.md: Use for the sharedccfa.yamlproject-state schema.
Maintenance Workflow
- Follow the current user scope and existing authorization before defaults; for no-new-files maintenance, edit existing surfaces only. When editing any CCFA family skill, preserve the
metadata.ccf_skill_controlsblock and keep its keys aligned withreferences/handoff-modes.md. - Use
references/routing.mdbefore adding new trigger language to prevent overlapping ownership. - Use
references/task-modes.mdbefore changing checklist strictness, quick polishing, standard review, or output contracts. - Use
references/review-output-standards.mdbefore changing scorecards, reviewer panels, score-risk language, or final output self-check rules. - Use
references/privacy-and-evidence.mdbefore adding any browsing, citation, novelty, scoring, experiment-result, compression, or rebuttal instruction. - Use
references/artifact-contracts.mdbefore changing generated filenames, revision behavior, report folders, caches, attempt archives, or ledgers. Default to one canonical artifact per deliverable, one stable working directory per task/artifact, and cleanup of task-created disposable files before delivery. Preserve required evidence and other tasks' files. - Never commit personal absolute paths, usernames, expanded home directories, private local skill roots, or machine-specific command examples. Use
$CODEX_HOME,$HOME, repo-relative paths, or non-identifying placeholders. - Put new public sources in
references/source-registry.yaml; do not duplicate long URL lists in siblingsource-notes.mdfiles. Local references must use repo-relative or non-identifyinglocal:/repo:identifiers, not machine paths. - Run
scripts/check_sources.pyafter source-registry edits. The script reports issues only and must not rewrite registry files. - Run
scripts/check_v04.pyfor family metadata, registry, script syntax, referenced resources, and regression checks; then runscripts/check_path_privacy.pybefore finalizing CCFA-family changes that touch docs, examples, source records, scripts, diagrams, or release files.
Output Contract
For ordinary preflight, return control to the specialist without a separate report. When auditing or updating CCFA skills, report:
Routing impact:
Handoff mode impact:
Private-material safety:
Source-registry changes:
Score-risk language changes:
Validation result:
Related Skills
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
