publish-report
Skill7 starsChanged 8 days agoMITView on GitHub
Publish a substantial Markdown completion report as a secret GitHub gist and send James its link via ntfy. Use when James asks for a phone-friendly report link after long-running or detailed work, or explicitly invokes this skill; do not use for ordinary brief handoffs.
In this repository19 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .agents/skills/autoreview/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-native-skills/AGENTS.mdAGENTS.md
- extensions/AGENTS.mdAGENTS.md
- autoreviewSkill
- axe-ios-simulatorSkill
- desktop-mac-releaseSkill
- dopplerSkill
- github-reference-finderSkill
- goal-writerSkill
- humanizerSkill
- mobile-testflightSkill
- ntfySkill
- qa-spiderSkill
- vercel-react-best-practicesSkill
- vercel-react-native-skillsSkill
- verified-bug-campaignSkill
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
- Distinctive: line 10
Check that it contains no credentials, tokens, private keys, or other material that should not be accessible by link.
- Very specific: line 12
Read and use the ntfy skill to send a concise completion notification containing the project or task name and the gist URL.
- Distinctive: line 15
If gist creation fails, do not send a misleading completion notification.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Publish Report
Finish the requested Markdown report, then:
- Check that it contains no credentials, tokens, private keys, or other material that should not be accessible by link. GitHub secret gists are unlisted, not access-controlled.
- Publish the report with
gh gist create. Keep the gist secret (the default; never pass--public), give it a descriptive.mdfilename, and capture the returned URL. - Read and use the
ntfyskill to send a concise completion notification containing the project or task name and the gist URL. - Include the gist URL in the normal final handoff as well.
If gist creation fails, do not send a misleading completion notification. Report the failure and preserve the Markdown report locally or in the final response.
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.

