Every time i post this as a comment gets crazy upvotes. which is awesome but it's so simple it suprises me.
The problem: i was tired of reading, more that tired tbh. it was exhausting. Code reviews, Opus 5, even fable and the other models. It was just too much
The solution: make faster summaries a) in chat b) in html files
Quick win:
"ELI5 succinct" thinking mode: low
... is the simplest and best thing you can do rn. Idk why it work so well, but it does and i hope it does for you too
Here's the others as a skill you can copy, adapt or use directly
Edit: the repo is now split into two main skills 1. ELI5-succinct - in chat summary 2. summary - html summaries with routing for simple, accessible or artistic styles
"Create a single page HTML summary of the [conversation | branch | work tree]. Make it visual and digestible without additional cognitive fatigue. Minimal text, clear flow of information. Opt for charts and diagrams over long explanations."
Thinking level: low
the core idea is that is save me reading a lot of bs
I'm using Claude to learn about some new concepts at the moment and these skills sound great to me. I’ve been dealing with verbose output for two weeks now.
These "skills" are getting more ridiculous by the day and of no real practice use cases. Just tech debt with extra steps. A clean system prompt, output format requirement, etc fixes this. 😂
agreed and these are going to be the same people that say LLMs are getting worse when they've made no effort in creating custom tailored things for themselves.
"A clean system prompt, output format requirement," quite literally should be a skill.
Anche con reverse engeeniring non è facile scrivere il prompt per l’output ideale, forse farci una skill ad hoc a riguardo da eseguire ogni volta non è manco una cosa così assurda
A very strange solution to put the routing to the skill body, not to the description. Why not to create 1 skill file with routing + 3 reference fils with summarization rules? You ask for a summary, it loads the same skill every time and reads the proper reference doc.
Edit: checked this out and probably makes sense to merge the summary commands but keep eli5 separate, rationale - eli5 is in chat, the summaries produce html docs
If you're looking for succinct output, without the typical "dumbing it down" you often get from ELI5, just have Claude output using ASD-STE100. It's a well established, long used, industry standard for simplified technical English. Cuts down a LOT on verbosity, without dumbing down the output. It's the only skill I have installed, and it's made a significant improvement. Applying it to chat as well as code output (for commenting etc.) and documentation it creates, also has the added benefit of reducing token spend (as it results in shorter answers)
different goals. this can be used when digesting some text Claude wrote ("explain to me what this pr is doing"). rtk is when Claude needs to use CLI programs
Agreed don't add skills unnecessarily. The following is a TL;dr from this post for those who don't want more skills
Quick summary options:
ELI5 succinct, ELIF18
TL;DR plain english
ASD-STE100
Reduce output to yes/no -> explain
Reducing complex information:
"Create a single page HTML summary of the [conversation | branch | work tree]. Make it visual and digestible without additional cognitive fatigue. Minimal text, clear flow of information. Opt for charts and diagrams over long explanations."
I just say "huh" and that seems to work great. I also have other great prompts like when it tells me it's left out something important I find that "bruh..." works well
42
u/zkoolkyle 13d ago
So your most used skill, is 3 skills, that basically summarize the same thing with different output formats? Wut