write-tech
Nine skills. You name the one you want. Each focused skill loads write-tech-core first. Claims need a source. Missing facts stay out of the draft.
SlopKit Skills
Name the document type
Ten Cursor skills for technical writing. Name the skill when you want
it applied. The write-tech set loads shared evidence rules from
write-tech-core.
npx skills add https://gitlab.techtailors.net/slopkit/skills.git \ --agent cursor \ --skill '*' \ --yes
Pack
10 skills
- 01 write-tech-core Shared evidence, audience, and verification rules.
- 02 write-tech-blog-post One claim, verified examples, an authorial voice.
- 03 write-tech-getting-started One verified path to a first visible success.
- 04 write-tech-how-to One task, exact commands, a check at the end.
- 05 write-tech-reference Lookup pages for commands, APIs, and schemas.
- 06 write-tech-readme Repository front door: try, use, navigate.
- 07 write-tech-pr-comment Review comments that ask for a change.
- 08 write-tech-pr-description Title and body for the review, not the diff.
- 09 write-tech-commit-message Subject and body for one coherent change.
- 10 refining-skills Patch a skill from a failing example, then re-run it.
What you install
The pack is GitLab slopkit/skills. Cursor copies each skill into ./.agents/skills/.
refining-skills
Use it when a skill already exists and someone shows a bad output plus what was wrong. Diagnose, reproduce, patch, verify. Do not edit from the comment alone.
Install them in this project
The getting-started path uses npx skills add for Cursor, then npx skills list --agent cursor. Ten names is the check.