SkillAgentSearch skills...

ccf-project-scaffolder

Initialize CCF project folders, LaTeX templates, artifact directories, and ccfa.yaml. Use for 项目初始化, 目录搭建, and paper template setup. Preserve existing files. Research codebase selection and training environments belong to ccf-research-engineer; workflow planning belongs to ccf-pipeline-orchestrator.

Install / Use

npx skills add mikubaka88/CCFA-Skills --skill ccf-project-scaffolder

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of ccf-project-scaffolder

ccf-project-scaffolder scores 81/100 on our quality scale, 2377th of 2,780 Automation skills we index.

Its SKILL.md is 4.4 KB long, split into 7 sections and no code examples: a solid amount of guidance for an agent.

With 2,825 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so ccf-project-scaffolder is actively maintained.
  • Our last check on 2026-11-08 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 found

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.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

ccf-project-scaffolder compared with similar skills

All 4 of these similar skills score higher than ccf-project-scaffolder; compare them before choosing.

SkillScoreStarsUpdatedFormat
ccf-project-scaffolder (this skill)by mikubaka88812.8k2mo agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install ccf-project-scaffolder?
Run npx skills add mikubaka88/CCFA-Skills --skill ccf-project-scaffolder. The install tabs above show the steps for each supported agent.
Which AI agents does ccf-project-scaffolder 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-project-scaffolder 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-project-scaffolder still maintained?
The repository was last updated about 2 months ago, so ccf-project-scaffolder is actively maintained.

name: ccf-project-scaffolder description: "Initialize CCF project folders, LaTeX templates, artifact directories, and ccfa.yaml. Use for 项目初始化, 目录搭建, template setup, and reproducible workspace scaffolding. Preserve existing files. Workflow planning belongs to ccf-pipeline-orchestrator; research content belongs to its specialist owner." metadata: ccf_skill_controls: handoff_question_mode: partial respect_session_denylists: true protect_idea_scope_in_writing: true private_material_safety: moderate shared_controls: ../ccf-common/references/

CCF Project Scaffolder

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 specialist execution, read and apply ccf-humanization first, then ccf-common. At every handoff, reuse their applicable active rules or refresh missing/changed ones. Both preflights are required even without prose; detailed editing, experiment, and maintenance modes run only when relevant.

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.

Invocation Controls

CCFA Handoff Mode: PARTIAL (Recommended). Follow metadata.ccf_skill_controls.handoff_question_mode, ../ccf-common/references/handoff-modes.md, and ../ccf-common/references/task-modes.md. A scaffold request authorizes the necessary local structure; a dry-run or no-new-files request limits changes accordingly.

Core Rule

Create the requested project structure, template, and state without inventing research content. Preserve existing user files and complete compatible missing pieces instead of replacing an established project.

Workflow

  1. Resolve the project location, venue, requested folders, and existing artifacts from the conversation and filesystem. Infer routine directory names; ask only about a consequential unresolved location or overwrite choice.
  2. Select the matching template through ../ccf-paper-writer/references/venue-guides/index.md. Verify that the template and its supporting style/assets are available. Use supplied templates when requested; identify unavailable dependencies precisely instead of copying an incomplete template.
  3. Resolve final artifacts and the working root through ../ccf-common/references/artifact-contracts.md. Create only needed directories and templates, with source/assets/cache/build subdirectories on demand. Preserve existing layout; do not migrate user files or overwrite a manuscript, bibliography, or configuration to refresh a scaffold.
  4. If ccfa.yaml is absent and initialization is requested, copy assets/ccfa.yaml, preserve the required fields in ../ccf-common/references/ccfa-yaml-contract.md, and fill only supplied project metadata. Existing state is read and updated only within the requested scope; unknown research fields remain explicit placeholders.
  5. Check the created paths, template references, and YAML. A build is useful when a runnable template was requested and an engine is available; do not run research experiments or final submission checks for directory setup.
  6. Report the actual created/updated paths and any concrete missing dependency. For a dry run, return the proposed tree and actions without writing files.

Boundaries

Use ../ccf-common/references/artifact-contracts.md for file ownership. Project workflow planning belongs to ccf-pipeline-orchestrator, manuscript prose to ccf-paper-writer, and final package checks to ccf-submission-checker. Do not invent a title, abstract, claim, experiment, or citation.

Related Skills

View on GitHub
GitHub Stars2.8k
CategoryAutomation
Updated2mo ago
Forks123

Languages

TeX

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions