repo-skill

Reuse repo-level skills defined in repository configurations across multiple repositories.

Updated Feb 28, 2026

Search Tags:#automation #workflow #config #sharing #skill #repo

Ready to run

npx skills add https://github.com/cjohnhanson/codelikecody --skill repo-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-skill
Source: https://github.com/cjohnhanson/codelikecody/tree/main/clc/tests/missouri/has-both-configs/repo-skills/repo-skill
Command: npx skills add https://github.com/cjohnhanson/codelikecody --skill repo-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repo-level skills reduce duplication by allowing teams to publish reusable capabilities once and apply them across many repositories.

Core Features & Use Cases

Centralized skill definitions that can be discovered and activated in multiple projects.
Optional extensions via scripts, references, and assets to tailor behavior per repo.
Easy onboarding of new team practices by adding or updating the SKILL.md in the repo.

Quick Start

Copy the repo-level SKILL.md into your project or reference it via your skill runner to activate shared automation.

Frequently Asked Questions about repo-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I reuse automation workflows across multiple code repositories?▼

To reuse automation workflows across multiple repositories, you can define a centralized SKILL.md file in your repo configuration. This allows standard automation patterns like onboarding and checks to be discovered and activated across different projects.

What is a repo-level skill configuration for?▼

A repo-level skill configuration is for reducing duplication by allowing teams to publish reusable capabilities once. By placing a root SKILL.md with YAML frontmatter in a repository, teams can apply shared development tasks across multiple projects.

How do I set up a shared repository skill for team onboarding?▼

To set up a shared repository skill for team onboarding, copy a repo-level SKILL.md into your project root. Include YAML frontmatter with name and description, and optionally add scripts, references, and assets directories to tailor the automation behavior.

Do I need dependencies to apply repo-level configs to my projects?▼

You do not need external dependencies to apply repo-level configs to your projects. The skill operates independently by requiring only a root SKILL.md file with YAML frontmatter to activate shared automation patterns across your repositories.

Can I extend repo-level skill behavior with custom scripts?▼

You can extend repo-level skill behavior by adding optional scripts, references, and assets directories alongside the root SKILL.md file. These extensions allow you to tailor standard automation patterns specifically for each repository's requirements.

What is the best way to standardize scaffolding tasks across development projects?▼

The best way to standardize scaffolding tasks across projects is using centralized skill definitions in a repo-level config. By maintaining a single SKILL.md, teams can ensure consistent onboarding and scaffolding automation applied uniformly across multiple repositories.