Teams often struggle to turn technical details into clear documentation. This skill structures READMEs, API references, tutorials, and guides for Claude, Codex, and Claude Code.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "technical-writer" from https://skillstore.io/skills/shubhamsaboo-technical-writer.md and its manifest at https://skillstore.io/api/skills/shubhamsaboo-technical-writer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "technical-writer". A CLI tool that sorts files by size and exports CSV results.
Expected outcome:
A README plan with a product summary, feature list, installation steps, quick start, usage examples, configuration notes, troubleshooting, and license section.
Using "technical-writer". A REST endpoint that creates projects and returns validation errors.
Expected outcome:
An API reference page with purpose, parameters, return values, example scenarios, error table, and guidance for common failures.
Using "technical-writer". A complex setup process for new developers joining a service team.
Expected outcome:
A tutorial outline with prerequisites, ordered setup steps, verification checks, common issues, and next steps for deeper learning.
All static findings were adjudicated as false positives after reviewing SKILL.md. The alerts point to markdown fences, inline placeholders, and sample documentation commands, not executable code or instructions to run commands. No prompt injection or data exfiltration intent was found.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
shubhamsaboo. (2026). technical-writer security audit report (audit version 2) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/shubhamsaboo-technical-writer/audits/2
BibTeX citation
@techreport{shubhamsaboo-shubhamsaboo-technical-writer-2026,
author = {shubhamsaboo},
title = {technical-writer security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/shubhamsaboo-technical-writer/audits/2},
note = {Author version 1.0.0}
}
CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "technical-writer security audit report (audit version 2)"
version: "1.0.0"
type: report
authors:
- name: "shubhamsaboo"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/shubhamsaboo-technical-writer/audits/2"
identifiers:
- type: other
value: "skillstore:shubhamsaboo-technical-writer:audit:2"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this scoreEvidence Confidence: Medium
55
Architecture
100
Maintainability
87
Content
65
Community
91
Spec Compliance
What You Can Build
Write Project READMEs
Turn project notes into clear README pages with setup, quick start, usage, and troubleshooting sections.
Document APIs
Create endpoint or function references that explain inputs, outputs, examples, errors, and edge cases.
Build User Guides
Create tutorials, onboarding guides, and support content for users learning technical workflows.
Try These Prompts
Create a README
Create a README for [project name]. Include the audience, project goal, key features, installation steps, quick start, common usage, troubleshooting, and license notes.
Document an API
Document this API using clear sections for purpose, parameters, return values, examples, errors, and edge cases. Use the source details I provide: [paste details].
Write a Tutorial
Write a beginner tutorial for [task]. Start with prerequisites, then provide numbered steps, expected results, common errors, and next steps.
Restructure Existing Docs
Review and restructure the following documentation for clarity, completeness, and scanning. Preserve technical meaning, remove duplication, identify gaps, and propose missing sections: [paste docs].
Best Practices
Provide the audience, product goal, and source details before requesting documentation.
Ask for examples, expected results, and common errors when creating guides.
Review generated commands, URLs, and configuration paths before publishing.
Avoid
Requesting complete documentation with no product context or source material.
Publishing generated command examples without verifying them in the target environment.
Mixing beginner setup steps and advanced reference details in one unstructured page.
Frequently Asked Questions
Can this skill create API documentation?
Yes. It can structure endpoint and function references with parameters, returns, examples, errors, and edge cases.
Does it test code samples?
No. It writes documentation and examples, but it does not run commands or verify code behavior.
Which tools can use this skill?
The report lists support for Claude, Codex, and Claude Code.
Can it improve existing documentation?
Yes. Provide the current text and ask for clearer structure, missing sections, or a specific style.
Can it write for non-developers?
Yes. Provide the audience level and ask for simpler wording, fewer assumptions, and more context.
What should I include in a prompt?
Include the audience, goal, source details, required sections, examples, and any style or terminology rules.