agentleFS
yuka-with-datayuka-with-data/skills/template/SKILL.md

template

Skill0 starsChanged 3 months agoMITView on GitHub

description of what this skill does and when it should be used.

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before using this skill, ensure the following requirements are met:

    line 28
  2. Distinctive:

    Use this skill when:

    line 41
  3. Distinctive:

    Follow this step-by-step process:

    line 54
  4. Distinctive:

    Keep outputs structured and predictable

    line 77
  5. Distinctive:

    Run the validation script:

    line 93

“Common” is measured: kept by at least 6 in 10 of the 6 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

[Template] Document Contributing Skill

Overview

Brief description of what the skill does in a concise and practical way

Explains:

  • primary purpose
  • expected workflow
  • major constraints

Prerequisites Checklist

Before using this skill, ensure the following requirements are met:

  • Python 3.8 or higher
  • Required Python dependencies
  • Valid authentication credentials
  • Required environment variables
  • Network access is available for external API or data source calls (if applicable)
  • Target tools or services used by this skill are accessible and operational

When to Use This Skill

trigger conditions

Use this skill when:

  • condition 1
  • condition 2
  • condition 3

Do NOT Use This Skill When

  • exclusion case 1
  • exclusion case 2

Execution Flow

Follow this step-by-step process:

  1. A
  2. B
  3. C
  4. D

Tool Guidance

Tool_name1

Purpose:

  • A
  • B

Key Rules:

  • Rule 1
  • Rule 2

Response Guidelines

  • Keep outputs structured and predictable
  • Avoid unnecessary verbosity
  • etc.

Error Handling

if execution fails:

  • Identify the cause
  • Provide fallback stragety if possible
  • etc.

Validation

File reference example

Run the validation script:

python scripts/validate_dataset.py data/my_dataset.csv

Progressive Disclosure

Load additional references only when relevant to the current task.

  • See references/example_references.md for specific tasks
  • See scripts/example_script.py for a specific script

Examples

Example 1

User: "Example request"

Flow:

  • Check prerequisites
  • Select tool
  • Execute
  • Format output

Example 2

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.