A writing guide for concise, searchable GitLab-style product and engineering documentation. It covers guides, configuration, administration, tutorials, troubleshooting, contributor documentation, and technical reference pages.

Use it to draft, rewrite, or audit technical documentation while preserving exact commands, labels, versions, settings, permissions, and documented results.

It helps documentation stay accurate and direct while separating confirmed behavior from workarounds, assumptions, and planned features.

gitlab-docs — Skill for Claude Code and Codex by Neeeophytee

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Neeeophytee/agent-stylebooks --skill gitlab-docs

Clone the repo

git clone --depth 1 https://github.com/Neeeophytee/agent-stylebooks

Made for: Claude Code, Codex.

Or install agent-stylebooks, the plugin that ships this one along with the rest of its 16 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/gitlab-docs/github.svg)](https://agentmods.dev/skills/neeeophytee/agent-stylebooks/gitlab-docs)

Your own site

<a href="https://agentmods.dev/skills/neeeophytee/agent-stylebooks/gitlab-docs"><img src="https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/gitlab-docs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/neeeophytee/agent-stylebooks/gitlab-docs"><img src="https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/gitlab-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 747 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00058	$0.00747
Opus 5.5	$0.00023	$0.00299
Sonnet 5.5	$0.00012	$0.00149
Haiku 4.5	$0.00006	$0.00075

Measured 2mo ago against content hash e7f3ca605146, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gitlab-docs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/gitlab-docs/SKILL.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitLab docs

Create brief, direct product documentation that functions as a trustworthy source of truth.

Preserve technical truth

Keep commands, code, product names, UI labels, versions, defaults, and results exact.
Do not convert an implementation detail into a product promise.
Separate confirmed behavior from a workaround, hypothesis, or planned behavior.
Ask for missing availability, permission, or version facts instead of inventing them.

Choose a topic type

Select one primary purpose per topic:

Concept: explain what something is, why it matters, and how parts relate.
Task: help the reader achieve one outcome through ordered actions.
Reference: present fields, options, syntax, or limits in a predictable structure.
Troubleshooting: connect a symptom to checks, causes, and recoveries.

Split a page when these purposes compete. A short context paragraph may introduce a task, but do not bury the first action under a conceptual essay.

Write from the customer's perspective

Lead with what the reader can accomplish or needs to know.
Address the reader as you for user actions. Name GitLab or another component when the product performs the action.
Prefer active voice, but use passive voice when the actor is irrelevant and the result is clearer.
Use concise, conversational sentences without chatty asides.
Keep one term for each feature. Match the product's visible labels and casing.
State facts and achievable outcomes. Qualify performance or security claims.
Write for translation: use explicit subjects, literal language, and straightforward sentence order.

Build tasks and troubleshooting

Put prerequisites, permissions, and availability before the steps.
Start steps with imperative verbs and keep each action observable.
Explain the expected result after the action.
Include verification when configuration changes are not immediately visible.
For failures, begin with the symptom the reader sees. Then give checks in the least expensive useful order and make recovery consequences clear.
Use fake data and reserved example domains. Never expose real credentials.

Read the full file on GitHub · 79 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 79 lines · 58 tokens per session scan A e7f3ca605146

Subscribe to this mod's changes

gitlab-docs is a skill published in the GitHub repository Neeeophytee/agent-stylebooks (78 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 747 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Writing and docs agent-skills content-design documentation gemini-cli openai-codex

gitlab-docs next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
gitlab-docsNeeeophytee/agent-stylebooks	Skill	78	2mo ago	MIT	A	58	Claude Code, Codex
readmethuanvd378/write-me-a-readme	Skill	2	3mo ago	MIT	A	103	Claude Code, Codex
yapperdzan314/yapper	Skill	1	6mo ago	MIT	A	54	Claude Code, Codex
spec-kitty-charter-doctrinePriivacy-ai/spec-kitty	Skill	1.7k	19d ago	MIT	A	135	Claude Code, Codex
mongodb-query-optimizerfcakyon/claude-codex-settings	Skill	1.2k	yesterday	Apache-2.0	A	98	Claude Code
chisle-auditJayPokale/Chisle	Skill	741	14d ago	MIT	A	130	Claude Code
crane-shotcafe3310/public-agent-skills	Skill	256	yesterday	Apache-2.0	A	25	Claude Code, Codex