unslop
Rewrite text so it reads like a person wrote it, not a template.
- License 许可
- MIT
- 所属仓库
- 0xr3ngar/bstack
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- unslop
- license
- MIT
- description
- Rewrite text so it reads like a person wrote it, not a template.
- compatibility
- No external tools required.
- disable-model-invocation
- true
02 资源文件 1
- 参考文档agents/openai.yaml43 B
03 SKILL.md 正文
Unslop
Rewrite the requested text so the reader can understand it on the first pass. Preserve the author's meaning and tone. Change wording only unless structural edits are in scope.
Edit the supplied files when asked to edit files. For pasted text, return the rewrite directly. Complete the edit instead of handing back a list of writing problems.
Make each sentence useful
- Replace vague praise with what something does. Cut sentences that add no fact, instruction, or necessary context.
- Remove filler, repeated conclusions, flattery, and support-chat endings.
- Replace anonymous authority such as "experts believe" with an existing source, or flag the unsupported claim. Never invent evidence.
- Preserve qualifications that affect the meaning. Shorter wording must not turn an estimate into a fact.
Use plain language
- Prefer "use" to "utilize" or "leverage", and "is" to "serves as".
- Replace abstract metaphors and stock phrases with the actual thing or action.
- State the point directly. Avoid "not just X, but Y", forced groups of three, and multiple synonyms for the same thing.
- Name the actor when it matters. Split sentences that require a second reading.
- Keep complete sentences. Do not compress prose into fragments, arrows, or unexplained abbreviations.
Keep formatting quiet
Use sentence case headings and only enough structure to help the reader. Remove decorative emoji, excessive bold, and labels that repeat their own explanation. Use periods or commas instead of dashes joining clauses.
Read the result once more for meaning and flow. Preserve commands, paths, numbers, citations, and direct quotes. Leave license text unchanged. If a factual problem needs work beyond the edit, name it briefly without pretending it was resolved.
04 同仓库更多 Skills
templates
暂无简介
yeet
Open a draft PR and work through the user's review comments. Once ready for review, explain feedback and wait for direction. Trigger on "yeet".
time-report
Estimate active work time from local Claude Code, Cursor, Codex, and Pi conversations and attribute it to tickets and PRs. Optionally log the hours to Jira. Use for 'how much time did I spend yesterday', 'find my conversations and how long they took', 'log my hours', morning time reports.
pr-debate
Review a PR with three subagents that argue over 2-3 rounds. A reviewer proposes comments, a skeptic argues they are noise, and a judge rules on each one. Use for /pr-debate, 'debate this PR', or an adversarial PR review.
no-comments
Remove redundant comments within the requested scope while preserving useful constraints and working code.
coding-best-practices
Implement or review code through a verified result. Keep changes small and TypeScript readable.