Project Skill Installer

Use this skill when the user says anything like:

• "为这个项目安装 skills"
• "给这个 repo 配 skills"
• "setup skills for this project"
• "install project skills"
• "update this project's skills"

This is an infrastructure skill. It installs profile selections and writes project routing docs; it does not replace frontend, presentation, bioinformatics, writing, or OpenAI system skills.

For current-machine update requests such as update presentations, update AI Skills, update Bridge Kit, or sync this machine, route first to machine-update-orchestrator. This installer owns only the AI_Skills manifest/profile/managed-block install or refresh step delegated by that orchestrator.

Workflow

1. Identify the target project root.

   • Prefer a user-specified path.
   • Otherwise use the current working directory.
   • If the current directory is inside a repo, use the repo root when obvious.

2. Locate the central AI_Skills_Collection repository.

   • First check the current directory and parent directories.
   • Then check common locations such as ~/AI_Skills_Collection,
     ~/AI_Skills/AI_Skills_Collection, /storage01/users/*/AI_Skills_Collection,
     and /project/*/*/AI_Skills_Collection.
   • If it cannot be found, ask the user for the path.

3. Run the unified installer from the central repository:

ai-skills install --target repo --project /path/to/project --profile ai-skills-maintainer --mode symlink --write-agents-md

If the user stated a domain or exact skill, install that selector directly:

ai-skills install --target repo --project /path/to/project --domain bayesian --mode symlink --write-agents-md
ai-skills install --target repo --project /path/to/project --skill domain/bayesian/pymc --mode symlink --write-agents-md

Examples:

• Writing a paper, literature review, submission, slides, or citations should
  route to research-main.
• Building a website, frontend, dashboard, React/Next.js app, or Tailwind UI
  should route to frontend-research-product.
• Bayesian, JSDM, HMSC, Stan, PyMC, MCMC, or simulation projects should route
  to codex-bayesian-jsdm.
• CMR, CardiacNexus, DICOM, NIfTI, MONAI, nnU-Net, or medical imaging projects
  should route to medical-imaging-project.
• Bioinformatics, single-cell, RNA-seq, VCF/BAM/GTF, scanpy, or scvi projects
  should route to bioinformatics-project.
• Maintaining AI_Skills_Collection itself should route to ai-skills-maintainer.

Legacy codex-* profile names remain available for compatibility with older
scripts. Prefer the v3 profile names above in new examples.

4. Read or re-read the generated project AGENTS.md.
   • The routing block lists the installed skills and their paths under
     .agents/skills/.
   • When a future task matches a listed trigger, read that skill's SKILL.md
     before acting.

Important Boundaries

• Complete domain installs are allowed when requested; treat budget output as warnings.
• Do not install the whole central library into global $HOME/.agents/skills or explicit codex-home skills.
• Do not clean or rewrite global skills when switching projects.
• Project skills belong in <project>/.agents/skills/.
• Explicit codex-home installs use ${CODEX_HOME:-$HOME/.codex}/skills only when the user asks for that advanced compatibility target.
• Do not migrate Codex Marketplace sources from main to release; that one-time bootstrap belongs to machine-update-orchestrator and must use official Codex Marketplace commands.