Borrowing it
Nothing to install: this file belongs to barateza/mcp-plesk-dev-docs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/barateza/mcp-plesk-dev-docs/main/.github/skills/docs-writer/SKILL.mdgit clone --depth 1 https://github.com/barateza/mcp-plesk-dev-docsWrote 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.
[](https://agentmods.dev/skills/barateza/mcp-plesk-dev-docs/docs-writer)<a href="https://agentmods.dev/skills/barateza/mcp-plesk-dev-docs/docs-writer"><img src="https://agentmods.dev/badge/skills/barateza/mcp-plesk-dev-docs/docs-writer/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.
<a href="https://agentmods.dev/skills/barateza/mcp-plesk-dev-docs/docs-writer"><img src="https://agentmods.dev/badge/skills/barateza/mcp-plesk-dev-docs/docs-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00026 | $0.00647 |
| Opus 5.5 | $0.00010 | $0.00259 |
| Sonnet 5.5 | $0.00005 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
docs-writer 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 1mo 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.
This is a copy
89% identical to docs-writer — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docs-writer skill instructions
As an expert technical writer and editor, your goal is to produce and refine documentation that is accurate, clear, consistent, and easy for users to understand. You must adhere to the documentation contribution process outlined in CONTRIBUTING.md.
Step 1: Understand the goal and create a plan
- Clarify the request: Fully understand the user's documentation request. Identify the core feature, command, or concept that needs work.
- Differentiate the task: Determine if the request is primarily for writing new content or editing existing content. If the request is ambiguous (e.g., "fix the docs"), ask the user for clarification.
- Formulate a plan: Create a clear, step-by-step plan for the required changes.
Step 2: Investigate and gather information
- Read the code: Thoroughly examine the relevant codebase, primarily within the
packages/directory, to ensure your work is backed by the implementation and to identify any gaps. - Identify files: Locate the specific documentation files in the
docs/directory that need to be modified. Always read the latest version of a file before you begin work. - Check for connections: Consider related documentation. If you change a command's behavior, check for other pages that reference it. If you add a new page, check if
docs/sidebar.jsonneeds to be updated. Make sure all links are up to date.
Step 3: Write or edit the documentation
- Follow the style guide: Adhere to the rules in
references/style-guide.md. Read this file to understand the project's documentation standards. - Ensure the new documentation accurately reflects the features in the code.
- Use
replaceandwrite_file: Use file system tools to apply your planned changes. For small edits,replaceis preferred. For new files or large rewrites,write_fileis more appropriate.
Sub-step: Editing existing documentation (as clarified in Step 1)
- Gaps: Identify areas where the documentation is incomplete or no longer reflects existing code.
- Tone: Ensure the tone is active and engaging, not passive.
- Clarity: Correct awkward wording, spelling, and grammar. Rephrase sentences to make them easier for users to understand.
- Consistency: Check for consistent terminology and style across all edited documents.
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.
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.
- 1mo ago First seen · 40 lines · 26 tokens per session scan A 7de94a3aef93
docs-writer is a skill published in the GitHub repository barateza/mcp-plesk-dev-docs (2 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 647 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to docs-writer, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
fastmcp-client-cli
Query and invoke tools on MCP servers using fastmcp list and fastmcp call. Use when you need to discover what tools a server offers, call tools, or integrate MCP servers into workflows.
code-review
Review code for quality, maintainability, and correctness.
reviewing-update-sets
Reviewing, analyzing, and comparing ServiceNow update sets before promotion, singly or in batches. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, 'what changed in…
triaging-incidents
Creating, triaging, updating, and analyzing ServiceNow incidents, including trend reports. Assess severity, check affected CIs, find related incidents, and recommend assignments. Use when the user mentions incidents, INC numbers, outages, service disruptions, ticket creation, triage, priority, severity, ITSM…
reviewing-sla-definitions
Reviewing ServiceNow SLA, OLA and underpinning-contract definitions and how they perform: breach rates per definition, overlapping or duplicated definitions on the same table and target, and definitions that never attach. Use when the user asks about SLA breaches by definition, too many SLAs, duplicate or conflicting…
vault-workflow
Use when the user asks you to search, read, or reason about notes in their markdown vault — guides when to use which vault tool and how to chain them for good results.