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
- Osipchuk/agent-skillstheir own version, first seen Nov 8, 2026
- TheMarnix/agent-config-kittheir own version, first seen Nov 1, 2026
- elastic/clients-team-automationstheir own version, first seen Oct 25, 2026
- kzndotsh/skillstheir own version, first seen Oct 17, 2026
- nakane1chome/claude-skillstheir own version, first seen Oct 15, 2026
- niklas-radyant/claude-skillstheir own version, first seen Oct 15, 2026
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- PaperDebugger/paperdebugger★ 1.5ksame name
- microsoft/GHCP-Lab★ 45same name
- chuckyatsuk/acidtest★ 8same name
- sigpanic/goink-skills★ 8same name
- niklas-radyant/claude-skills★ 6same name
- Osipchuk/agent-skills★ 5same name
- kzndotsh/skills★ 2same name
- sarveshtalele/mcp-skills-registry★ 2same name
- sumulige/sumulige-claude★ 2same name
- elastic/clients-team-automations★ 1same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- bluetoothSkill
- daily-device-briefSkill
- mailSkill
- RoutePlanningNavigationSkillSkill
- OpenAppSkillSkill
- shoppingSkill
- web researchSkill
- wifiSkill
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
- Distinctive: line 11
Use this skill when the user wants to:
- Distinctive: line 16
Do NOT use this skill when:
- Very specific: line 30
Call tool_name_1 with the necessary parameters.
- Distinctive: line 31
Check the result. If successful, proceed to step 3.
- Distinctive: line 32
If the result indicates an error, inform the user and suggest next steps.
- Very specific: line 33
Call tool_name_2 to complete the task.
- Distinctive: line 37
Ask the user for any missing information (e.g., destination, account name).
- Very specific: line 38
Call tool_name_1 with the confirmed parameters.
- Distinctive: line 43
Always confirm with the user before performing destructive or high-risk actions.
- Distinctive: line 44
Never expose sensitive data (passwords, tokens) in responses or tool parameters.
- Distinctive: line 45
If a tool returns missing permission, guide the user to grant the permission first.
- Distinctive: line 58
Stop and notify the user when:
“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.
Files
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
- Call
tool_name_1with the necessary parameters. - Check the result. If successful, proceed to step 3.
- If the result indicates an error, inform the user and suggest next steps.
- Call
tool_name_2to complete the task.
2. Alternative Scenario
- Ask the user for any missing information (e.g., destination, account name).
- Call
tool_name_1with the confirmed parameters. - 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.
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
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.

