agentleFS
FoneClaw-AIFoneClaw-AI/foneclaw-android/skills/_template/SKILL.md

my-skill

Skill21 starsChanged 4 months agoMITView on GitHub

A one-line summary describing what this skill helps the agent accomplish.

18 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

12 rules. 0 are common, 9 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user wants to:

    line 11
  2. Distinctive:

    Do NOT use this skill when:

    line 16
  3. Very specific:

    Call tool_name_1 with the necessary parameters.

    line 30
  4. Distinctive:

    Check the result. If successful, proceed to step 3.

    line 31
  5. Distinctive:

    If the result indicates an error, inform the user and suggest next steps.

    line 32
  6. Very specific:

    Call tool_name_2 to complete the task.

    line 33
  7. Distinctive:

    Ask the user for any missing information (e.g., destination, account name).

    line 37
  8. Very specific:

    Call tool_name_1 with the confirmed parameters.

    line 38
  9. Distinctive:

    Always confirm with the user before performing destructive or high-risk actions.

    line 43
  10. Distinctive:

    Never expose sensitive data (passwords, tokens) in responses or tool parameters.

    line 44
  11. Distinctive:

    If a tool returns missing permission, guide the user to grant the permission first.

    line 45
  12. Distinctive:

    Stop and notify the user when:

    line 58

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

My Skill

Scope / Applicable Scenarios

Use this skill when the user wants to:

  • Scenario A: what triggers it and what the user expects.
  • Scenario B: another common trigger.

Do NOT use this skill when:

  • The task is outside this skill's domain.
  • Another skill is more appropriate.

Available Tools

  • tool_name_1: Brief description of what this tool does and its key parameters.
  • tool_name_2: Brief description.

Recommended Workflows

1. Primary Scenario

  1. Call tool_name_1 with the necessary parameters.
  2. Check the result. If successful, proceed to step 3.
  3. If the result indicates an error, inform the user and suggest next steps.
  4. Call tool_name_2 to complete the task.

2. Alternative Scenario

  1. Ask the user for any missing information (e.g., destination, account name).
  2. Call tool_name_1 with the confirmed parameters.
  3. Present the result clearly to the user.

Rules / Agent Behavior Requirements

  • Always confirm with the user before performing destructive or high-risk actions.
  • Never expose sensitive data (passwords, tokens) in responses or tool parameters.
  • If a tool returns missing permission, guide the user to grant the permission first.
  • Handle empty results gracefully — explain possible causes rather than stating "nothing found."

Completion Criteria

The task is complete when:

  • The requested information has been presented to the user.
  • The requested action has been executed successfully.
  • The user has been clearly informed of any required manual steps or limitations.

Failure Conditions

Stop and notify the user when:

  • Required permissions are missing and the user declines to grant them.
  • A tool fails after a reasonable retry attempt.
  • The user's request is ambiguous and they cannot provide clarification.

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.