Technical Writer
Eleven technical-writing skills built on one core style guide: conclusion first, every claim traced to a source, one fact in one place, and a list of banned constructions. The specialised skills cover design documents and RFCs, architecture decision records, changelogs and release notes, runbooks, tracker issues, postmortems, documenting legacy codebases, process diagrams, API and payload references, and reviewing someone else's technical prose. Aimed at engineers and technical writers who want documents in a consistent, verifiable house style.
- Technical writing
- Code documentation
Source: riekelt/technical-writer · pinned commit 099d31b
View source on GitHubLuluSkill lists this project so you can find it. A listing is not a security review or an endorsement, and nothing on this page is installed or run for you.
EDITORIAL GUIDE
Choose the technical document before choosing the wording
A runbook, decision record and interface contract have different obligations. Structure helps only when conclusions remain grounded in the supplied evidence.
LuluSkill’s own reading of this project, not a summary of its README. About 3 minutes to read
This guide is LuluSkill’s own judgement about when this project fits, written from the pinned version named above. It is not the author’s documentation, not a security review and not a recommendation. LuluSkill did not install, run or test the project to write it, and the guide is shown only while this listing still points at the commit it was written against.
When this project fits
Use this collection when a specific technical document needs a consistent structure and traceable conclusions. The README groups specializations such as decision records, runbooks and contracts under a strict house style, making document type the useful first selection.
When to choose something else
Do not rewrite a normative policy to match a broken implementation simply to eliminate disagreement. An incident report must also distinguish observed events from hypotheses. A tidy structure cannot supply missing operational evidence, decisions or approval history.
What to provide and what to expect
Provide the document type, reader, source facts and decisions that are already approved. Expect a draft organized around that purpose, with gaps clearly marked. Keep each maintained fact in an identifiable home so later updates do not create contradictory copies.
Tools, permissions and boundaries
Supplied documents may be enough for drafting. Repository inspection or writes need scoped access, and host-specific agents or commands require compatible setup. Referencing a command in a runbook is not authority to execute it against a live service.
The tradeoff and an alternative
A small template may be sufficient for one well-understood document. The collection adds value when several document types need disciplined consistency. Its cost is reconciling the house style with your organization’s actual obligations rather than imposing format over substance.
A small acceptance exercise
Proposed exercise: draft a runbook from one known failure and recovery procedure. Check the trigger, prerequisites, verification and escalation separately. Reject instructions with invented access, unexplained destructive steps or a recovery claim that has no supporting record.
Source, version and what was actually read
The pinned README introduction, house-style principles and document-specialization list were read. Individual templates, commands and actual operational procedures were not evaluated. LuluSkill did not install or run this project; the exercise above is a proposed reader check, not a reported result.
How to use this listing
LuluSkill publishes the description and the source link only. The skill itself stays in its author’s repository, and nothing here is installed, copied or run for you.
- Read what the skill helps with The summary above says which job the project is for. If that is not the job you have, this is probably not the listing you want.
- Open the original source and follow the author’s own instructions The link to the original project opens its author’s page. That page, not this one, is where the setup steps and any copying instructions live.
- Use it in a compatible AI assistant Skills of this kind are normally used inside an AI assistant that can read a folder of files on your computer. Which assistants support them is the author’s decision, so check their page before you start.
Who it is for
Somebody who already wants this one job done and is willing to follow the author’s setup steps. No programming knowledge is assumed, and this listing cannot tell you whether the project suits you.
Before you start
You need an AI assistant that supports skills, and you will be following somebody else’s instructions on your own computer. Read them before you run anything.
What you end up with
Whatever the author’s project produces. LuluSkill never runs it, so this page cannot promise a result, a file, or a level of quality.
Where it is normally used
Projects like this are usually used in an AI assistant that supports skills, such as an AI coding assistant. The author’s repository says which assistants it is written for; LuluSkill has not tested it with any of them.
Version checked
The source was checked at this commit: 099d31b
Changes made to the repository after this commit have not been checked.
License
MIT, from the licence file in the source repository at the listed commit. Check the repository’s licence before you use or copy the project.
Listing only
LuluSkill lists this project only. It does not host, download or run its code.
What this page does not include
The project’s files and setup steps stay in its own repository. LuluSkill has not security-tested the project or confirmed which AI assistants it works with.
Report a problem or request removal
Rights holders and users can report licence, attribution, security or accuracy problems with this page. We respond within 48 hours and record every request in our review log.
Opens your email app. You can also write to contact@luluskill.com and include this page’s address.