copydesk
Skill1 starsChanged 2 months agoMITView on GitHub
Use when a Markdown file was written through Bash, needs an on-demand prose check, or passed through the gate after three failed attempts.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- gigio1023/agent-skillstheir own version, first seen Oct 13, 2026
- gigio1023/gigio-skillstheir own version, first seen Oct 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- gigio1023/agent-skills★ 2same name
- gigio1023/gigio-skills★ 2same 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.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
Use this skill to check Markdown that the Write and Edit gate cannot see.
- Distinctive: line 12
Run the CLI against the named file:
- Distinctive: line 20
Do not edit the file. Do not install this skill or enable the hook as part of a check.
≈ “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
CopyDesk check
Use this skill to check Markdown that the Write and Edit gate cannot see. Bash writes through cat, tee, sed, or a heredoc bypass that gate.
The copydesk CLI must already be on PATH. A checkout owner can expose it once with install.sh. Do not run that installer as part of a check.
Run the CLI against the named file:
copydesk check path/to/document.mdIf the command is unavailable, say that the CLI needs installing and stop. Report the resolved channel and command output with its line numbers. Exit 0 means clean or warnings only; exit 1 means findings that would block a write. If an AI-tell error appears in a human-facing document, suggest /humanizer.
Do not edit the file. Do not install this skill or enable the hook as part of a check.
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.