Tldr
Quick plain-language brief — skip the explanation, get the point. Use when the user says "tldr", "quick version", "what is X", "should I use X", "just tell me", "give me the short version", or is clearly in a hurry. Output adapts to the question: - Pure definition ("what is X") → 1 sentence + 1-2 key facts - Decision / comparison ("should I use X", "X vs Y") → 1 sentence + use when / skip when / bottom line Max 5 lines. No diagrams. No analogies. No history. Direct verdict.From its SKILL.md
npx -y skills add Jsnnmsc/10000x-engineer --skill tldrAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 248 tokens by cl100k_base, as published. Nobody here has run it
TL;DR
Goal: user reads this in 10 seconds and knows what to do.
Rules
- Respond in the same language the user wrote in. If they write in Chinese, reply in Chinese. Technical terms (JWT, Redis, API…) stay in English.
- Max 5 lines. Hard limit.
- No diagrams, no analogies, no history.
- Every word earns its place.
Detect the intent, pick the format
If the question is a definition ("what is X", "explain X briefly"):
**$ARGUMENTS**
[One sentence. What it does in plain language.]
- [Key fact #1]
- [Key fact #2]
If the question involves a decision ("should I use X", "X vs Y", "is X worth it"):
**$ARGUMENTS**
[One sentence. What it does in plain language.]
- Use it when: [one condition, ≤8 words]
- Skip it when: [one condition, ≤8 words]
- Bottom line: [direct recommendation or verdict]
If $ARGUMENTS is empty, ask: "Quick brief on what?"
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.