make
Skill1 starsChanged 8 months agoMITView on GitHub
List or run Makefile targets
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ojt3492/claude-skillstheir own version, first seen Oct 17, 2026
- suntay44/motionabletheir own version, first seen Oct 17, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- suntay44/motionable★ 12same name
- ojt3492/claude-skills★ 0same name
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.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
If arguments are given, run make $ARGUMENTS via Bash.
- Distinctive: line 10
If no target is specified, show the project's available workflows from the Makefile target table in session context.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
If arguments are given, run make $ARGUMENTS via Bash.
If no target is specified, show the project's available workflows from the Makefile target table in session context. Group by permission level (read, write, danger). Include the recipe column — it shows what each target actually runs and helps the user decide.
Suggest targets that are relevant to what the user has been doing:
- Wrote or changed code → lint, test, format, typecheck
- Starting on the project → setup, install, dev
- Investigating the project → help, status, list
- Preparing to ship → build, test
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.