#geterdone — Public Fediverse posts

Here's a bit that will save you time and ache with bigger projects that require more personalization or custom instruction... Skills let you package a workflow once and have Claude reach for it automatically. A few things make the difference between one that gets used and one that just sits there:
The description is everything. It's how Claude decides whether to use your skill at all, so spell out what it does and when to use it. Be a little pushy here — list the trigger phrases and contexts, because the bigger risk is Claude under-using a good skill, not over-using it.
Keep the main file lean. A skill loads in layers: the name and description are always in context, the body loads when the skill triggers, and anything bundled (reference docs, scripts, templates) loads only when needed. Aim to keep the core instructions tight and push heavy detail into separate reference files.
Write it like you're briefing a sharp teammate. Use direct, imperative steps, and explain why something matters instead of stacking up rules in all caps. Tone of "here's the reasoning" beats a wall of MUSTs.
Show, don't just tell. A quick input/output example or a fixed template communicates more than a paragraph of description.
Test it like a real user would. Write two or three prompts the way someone would actually phrase them, run them, and check two things: did the skill trigger, and did it produce what you wanted? Then revise and repeat.
And the golden rule: no surprises. The skill should do exactly what its description implies — nothing hidden.
#Claude #AI #Anthropic #GetErDone

Must plan all the things...

#GetErDone #Planning #ToDoList #2do2day

If my students can do it, I can do it!
#wordcount #amwriting #GetErDone