agentsclimarketplace
Sign in

Project skill template

Skill kyt19970215/codex-skill-evolution-framework/templates/project-skill-template

Template project skill for a named project or repo. Rename this folder and frontmatter before use. Use for project-specific source priorities, local paths, commands, domain terms, decisions, known issues, semantic rule capture, and failure-learning entries that should not live in global skills.From its SKILL.md

Install
npx -y skills add kyt19970215/codex-skill-evolution-framework --skill project-skill-template

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, 443 tokens by cl100k_base, as published. Nobody here has run it

Example Project

Use this skill as the project rule layer for a named project. Replace placeholders before using it for real work.

First Steps

  1. Treat the current user request and current local files as the source of truth.
  2. Read references/project-rules.md before making non-trivial project decisions.
  3. Read references/local-map.md when you need paths, script names, generated outputs, or stable local commands.
  4. Read references/sources.md before broad public research.
  5. Read references/known-issues.md when a failure looks project-specific or when the user asks to save a project lesson.
  6. When the user gives a clear project-scoped durable rule marker, capture the rule into the narrowest project reference instead of requiring the user to say "add this to skill" every time.

Collaboration Rules

  • Use the user's preferred language unless project policy says otherwise.
  • Lead with conclusion, then evidence, risk, and next step.
  • Avoid presenting inference as fact.
  • For new scripts, reports, previews, or output artifacts, include local links in the final answer when appropriate.

Project Rule Capture

  • Put project website/source/search-order preferences in references/sources.md.
  • Put project workflow, communication, safety, architecture, and verification standards in references/project-rules.md.
  • Put stable local commands, paths, generated outputs, and repo map details in references/local-map.md.
  • Put recurring project-specific failures in references/known-issues.md.
  • Put durable architecture decisions in references/decisions.md.
  • If the user says only "add a rule" after a project instruction, look back at the immediately preceding user message and extract the durable project rule.

References

  • references/project-rules.md: durable project requirements and workflow rules.
  • references/local-map.md: stable paths, commands, outputs, and local structure.
  • references/sources.md: project-specific source priority and research rules.
  • references/known-issues.md: recurring project-specific symptoms, root causes, guardrails, and verified fixes.
  • references/decisions.md: durable project decisions and evidence.

What ships with it: 6 files

2.5 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.