agentleFS
Sign inStart free
Dqz00116Dqz00116/skill-lib/contributing/SKILL.md

contributing

Skill22 starsChanged 7 months agoMITView on GitHub

Use when contributing new skills to the skill-lib repository, installing skills locally, or verifying skill compliance with repository standards

  • Deletes or force-pushes

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use e2e, worktree and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    e2e

    Run E2E tests for Sentry JavaScript SDK test applications

    Also in 3 projects that use this

  • MicrosoftSkill

    worktree

    Create, reuse or clean up a dedicated git worktree for working on a pull request or a private branch. Use from any PR-scoped workflow that needs an isolated checkout to keep current code and build output untouched.

    Also in 3 projects that use this

  • NVIDIASkill

    testing

    Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Remove specific project paths

    line 91
  2. Distinctive:

    Check for duplicate skills

    line 98
  3. Very specific:

    Create skill-name/SKILL.md following standards

    line 99
  4. Very specific:

    Run python scripts/generate-summary.py --write to update index

    line 101

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Contributing to Skill-Lib

Guidelines for installing skills and contributing new ones to this repository.

Overview

Skill-Lib is a curated collection of reusable AI Agent Skills. Each skill follows the writing-skills standard with standardized frontmatter, structure, and content guidelines.

When to Use

  • Adding a new skill to this repository
  • Installing skills to your local workspace
  • Updating existing skills to meet repository standards
  • Understanding naming conventions and file structure requirements

Quick Reference

ActionCommand / Step
Install all skillsgit clone https://github.com/Dqz00116/skill-lib.git then copy directories
Install single skillDownload skill-name/SKILL.md to ~/workspace/skills/skill-name/
Add new skillCreate skill-name/SKILL.md following standards below
Update indexpython scripts/generate-summary.py --write

Installation

Install All Skills

git clone https://github.com/Dqz00116/skill-lib.git /tmp/skill-lib
mkdir -p ~/workspace/skills
cp -r /tmp/skill-lib/*/ ~/workspace/skills/
rm -rf /tmp/skill-lib

Install Single Skill

mkdir -p ~/workspace/skills/code-analysis
curl -o ~/workspace/skills/code-analysis/SKILL.md \
  https://raw.githubusercontent.com/Dqz00116/skill-lib/main/code-analysis/SKILL.md

Verify Installation

Each skill must contain:

skill-name/
└── SKILL.md          # Required

Optional: README.md, templates/, examples/, scripts/.

Contributing

Naming Conventions

ItemFormatExample
Directory namelowercase + hyphenscode-analysis
SKILL.md filenameuppercaseSKILL.md
name fieldmatches directorycode-analysis
descriptionstarts with Use when...Use when analyzing unfamiliar code

SKILL.md Standards

Required frontmatter:

---
name: skill-name
description: Use when [triggering conditions]
---

Required sections:

  • ## Overview — 1-2 sentence summary
  • ## When to Use — triggering conditions and anti-cases

Recommended sections:

  • ## Quick Reference — tables for scanning
  • ## Common Mistakes — what goes wrong and fixes

Content Guidelines

Must sanitize:

  • Remove specific project paths
  • Remove personal information
  • Remove company-specific code
  • Use generic examples

Submission Process

  1. Check for duplicate skills
  2. Create skill-name/SKILL.md following standards
  3. Sanitize all content
  4. Run python scripts/generate-summary.py --write to update index
  5. Submit via Pull Request

Common Mistakes

MistakeFix
Missing ## OverviewAdd 1-2 sentence summary after title
description describes workflowRewrite to start with Use when...
Directory name uses camelCaseUse lowercase + hyphens
Specific paths in examplesReplace with generic placeholders
Forgetting to update indexRun generate-summary.py --write

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free