SkillsAdd

mikubaka88/ccfa-skills

ccf-project-scaffolder

Initialize CCF project folders, LaTeX templates, artifact directories, and ccfa.yaml.

Trending #2620 Hot #6212 First seen Jun 10, 2026

Installation

$ npx skills add mikubaka88/ccfa-skills --skill ccf-project-scaffolder
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from mikubaka88/ccfa-skills · top by installs.

npx skills add mikubaka88/ccfa-skills
ccf-paper-writer 45 ccf-common 2 ccf-integrity-auditor 45 ccf-paper-reviewer 44 ccf-experiment-designer 2 ccf-literature-searcher 45 ccf-idea-optimizer 2 ccf-idea-reviewer 2 ccf-visual-composer 43 ccf-literature-monitor 2

Browse all from mikubaka88/ccfa-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2.3K
License LICENSE
Default branch main
Open issues 4
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More 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\/"}

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,084 B
  • docs SUMMARY.md 341 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 713 installs

SKILL.md

CCF Project Scaffolder

Invocation Controls

CCFA Handoff Mode: PARTIAL (Recommended). Follow metadata.ccfskillcontrols.handoffquestionmode, ../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.