tech-doc
Write Clear Technical Documentation
Technical teams lose time when docs mix assumptions, unclear scope, and hard-to-scan instructions. This skill helps Claude, Codex, and Claude Code produce structured, cited, and maintainable technical documents.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "tech-doc" from https://skillstore.io/skills/dcjanus-tech-doc.md and its manifest at https://skillstore.io/api/skills/dcjanus-tech-doc/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.
Test it
Using "tech-doc". Rough notes describe a new caching feature and several edge cases.
Expected outcome:
A reader-scoped explanation with a one-sentence conclusion, key behaviors, boundaries, examples, and a list of items needing confirmation.
Using "tech-doc". A team needs a repeatable deployment checklist from scattered chat notes.
Expected outcome:
A concise SOP with prerequisites, risk warnings, the shortest safe path, common errors, and links to authoritative references.
Using "tech-doc". A Markdown guide has long sections, inconsistent terms, and weak citations.
Expected outcome:
A cleaned document structure with shorter sections, consistent terminology, explicit citation gaps, and publication-ready formatting notes.
Security Audit
SafeThe static command finding is a false positive because SKILL.md line 23 describes how to format shell examples in documentation. The entropy alert is also a false positive; the file is coherent Markdown text with Chinese content, not obfuscated or encrypted data. No prompt injection or malicious semantic intent was found.
Risk Factors
⚙️ External commands (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/dcjanus-tech-doc/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dcjanus-tech-doc?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dcjanus-tech-doc?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dcjanus-tech-doc/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dcjanus-tech-doc.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
DCjanus. (2026). tech-doc security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dcjanus-tech-doc/audits/8BibTeX citation
@techreport{dcjanus-dcjanus-tech-doc-2026,
author = {DCjanus},
title = {tech-doc security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/dcjanus-tech-doc/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "tech-doc security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "DCjanus"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/dcjanus-tech-doc/audits/8"
identifiers:
- type: other
value: "skillstore:dcjanus-tech-doc:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Create Feature Documentation
Turn implementation notes into a scoped explanation with reader assumptions, outcomes, boundaries, and supporting evidence.
Write Operational SOPs
Build a concise procedure with prerequisites, risk notes, copyable examples, common errors, and related references.
Standardize Team Docs
Define shared rules for Markdown structure, citations, terminology, command examples, and review handoffs.
Try These Prompts
Use the tech-doc skill to draft a short explanation document from these notes. State the goal, reader, scope, and outcome first.
Use the tech-doc skill to rewrite this document. Keep facts unchanged, reduce assumptions, tighten headings, and mark any missing information.
Use the tech-doc skill to create an SOP. Include scope, prerequisites, risk notes, shortest safe example, common errors, and references.
Use the tech-doc skill to review this technical document. Identify unsupported claims, unclear terms, missing citations, risky examples, and maintenance gaps.
Best Practices
- Provide source notes, target reader, scope, and required terminology before asking for a draft.
- Ask the assistant to mark uncertain facts instead of filling gaps from assumption.
- Review command examples, permissions, and references before publishing operational documents.
Avoid
- Do not ask the skill to invent missing facts, metrics, or unsupported conclusions.
- Do not publish command examples without reviewing permissions, placeholders, and dry-run options.
- Do not mix tutorials, references, and SOPs without a clear reader goal.