tweet
Skill1 starsChanged 4 months agoMITView on GitHub
Draft or revise ready-to-copy tweets without scheduling or publishing them. Use when the user invokes /tweet or asks to turn an idea, source, or existing draft into a concise X post or, when explicitly requested, a short thread.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- RichardBray/skillstheir own version, first seen Sep 29, 2026
- kkoppenhaver/cc-skillstheir own version, first seen Mar 23, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- RichardBray/skills★ 5same name
- kkoppenhaver/cc-skills★ 4same 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agentic-osSkill
- captureSkill
- domain-reconnaissanceSkill
- lookupSkill
- orchestrateSkill
- postSkill
- setup-agentic-osSkill
- setup-career-systemSkill
- setup-knowledge-systemSkill
- setup-mastery-systemSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create concise social copy in the conversation.
- Distinctive: line 14
If the brief is already usable, draft immediately.
- Distinctive: line 16
Use facts and source material supplied by the user first.
- Very specific: line 18
When personal or project context would materially improve accuracy, optionally invoke an available read-only /lookup capability with the …
- Distinctive: line 22
Write one self-contained tweet by default.
- Distinctive: line 25
Prefer a concrete opening, plain language, and one memorable point.
- Very specific: line 35
Treat an unavailable capability, a search miss, absent, or unresolved as unavailable optional context.
- Distinctive: line 38
Do not turn a failed optional lookup into a blocker unless the user explicitly requires facts that cannot otherwise be verified.
- Distinctive: line 48
Never imply that returned copy has been saved, scheduled, queued, or published.
≈ “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
Tweet
Create concise social copy in the conversation. This skill is an authoring surface, not a publishing action.
Workflow
- Identify the core point, audience, desired response, and tone from the request. If the brief is already usable, draft immediately. Ask a question only when a missing choice would materially change the result.
- Use facts and source material supplied by the user first. Do not invent claims, results, quotations, dates, or personal experience.
- When personal or project context would materially improve accuracy, optionally
invoke an available read-only
/lookupcapability with the narrowest request needed for this tweet. Request only relevant facts or voice guidance, never broad background. - Write one self-contained tweet by default. Aim for 280 characters or fewer, including URLs as written. Create a thread only when the user explicitly asks for one or approves expanding material that cannot fit honestly.
- Prefer a concrete opening, plain language, and one memorable point. Remove throat-clearing, repeated setup, filler, and unnecessary hashtags. Preserve the user's voice rather than forcing a generic social-media style.
- Return the ready-to-copy tweet first. Add alternatives or a brief constraint note only when useful.
Optional Knowledge Context
- Depend only on the public behavior of
/lookup; do not inspect or name its provider, storage layout, bindings, or internal traversal. - Treat an unavailable capability, a search miss,
absent, orunresolvedas unavailable optional context. Continue from the user's prompt and disclose the limitation only when it affects confidence in the copy. - Do not turn a failed optional lookup into a blocker unless the user explicitly requires facts that cannot otherwise be verified.
Authority Boundary
- Author copy locally in the response. Do not create a remote draft, schedule a tweet, publish content, or call a social publishing tool.
- A request that combines authoring and publishing does not expand this skill's authority. Produce the copy, then state that scheduling or publishing requires a separate explicit publishing action.
- Never imply that returned copy has been saved, scheduled, queued, or published.
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.