linkedin-case-receipt
Skill0 starsChanged 39 days agoMITView on GitHub
Draft a proof post from a build log: what shipped, what failed, what the log showed. Use for systems, audits, and operator work. Not for motivational posts.
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- llms.txtllms.txt
- linkedin-marketingSkill
- agent-instagram-deskSkill
- agent-whatsapp-deskSkill
- agent-x-deskSkill
- agent-youtube-deskSkill
- linkedin-analytics-reviewSkill
- linkedin-approval-gateSkill
- linkedin-carousel-writerSkill
- linkedin-comment-drafterSkill
- linkedin-connection-noteSkill
- linkedin-content-plannerSkill
- linkedin-correctionSkill
- linkedin-cta-labSkill
- linkedin-employee-advocacySkill
- linkedin-engager-analyticsSkill
- linkedin-event-noteSkill
- linkedin-experience-bulletSkill
- linkedin-feature-pickerSkill
- linkedin-first-commentSkill
- linkedin-headline-labSkill
- linkedin-hook-extractorSkill
- linkedin-hook-labSkill
- linkedin-humanizerSkill
- linkedin-interviewerSkill
- linkedin-ist-windowSkill
- linkedin-job-answersSkill
- linkedin-job-fitSkill
- linkedin-job-intakeSkill
- linkedin-job-logSkill
- linkedin-job-noteSkill
- linkedin-newsletterSkill
- linkedin-poll-writerSkill
- linkedin-post-writerSkill
- linkedin-profile-optimizerSkill
- linkedin-quote-commentSkill
- linkedin-reply-handlerSkill
- linkedin-repurposerSkill
- linkedin-series-builderSkill
- linkedin-silence-auditSkill
- linkedin-thread-monitorSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
No emoji. No hashtag block.
- Distinctive: line 27
If the evidence is a private log, paraphrase.
≈ “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
Case receipt
A post that can survive a skeptic. Built for operators who ship systems.
When to use
- "Write the post for this deploy"
- "Turn this incident note into a LinkedIn post"
- "Receipt, not a launch announcement"
Steps
- Require three fields: what changed, what broke or was risky, what evidence exists. If one is missing, ask. Do not fill it.
- Shape: hook with the object, the constraint, the move, the evidence, the limit.
- Length 900 to 1,300 characters. Hook inside 210.
- Ban launch voice: excited, thrilled, proud to announce.
- Show the draft and the missing-evidence list. Wait for post.
Hard rules
Global voice rules: see root SKILL.md Voice rules.
- No emoji. No hashtag block.
- Name the system only if the user named it.
- If the evidence is a private log, paraphrase. Do not ask the user to paste secrets.
Related
linkedin-post-writerlinkedin-humanizerlinkedin-approval-gate../../references/voice-rules.md../../references/operator-codesbyfebin.md
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.