stow
Standardize Technical Writing with STOW
Technical documents often lose precision when prose, commands, paths, and structured data are edited inconsistently. STOW applies output contracts and focused prose review while preserving protected literals.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
Review the Skillstore skill "stow" from https://skillstore.io/skills/theislampill-stow.md and its manifest at https://skillstore.io/api/skills/theislampill-stow/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„stow“ wird verwendet. Rewrite a deployment README while preserving its commands and configuration names.
Erwartetes Ergebnis:
A concise README with the installation path first, direct headings, consistent terminology, and unchanged commands and configuration names.
„stow“ wird verwendet. Review a migration runbook for operational completeness.
Erwartetes Ergebnis:
- Add a precondition stating the required backup and access checks.
- Add a verification result and rollback action to the migration step.
- Keep the existing service name, command text, and evidence references unchanged.
„stow“ wird verwendet. Check a handoff artifact against its schema and report the result.
Erwartetes Ergebnis:
The report separates parse failures, schema violations, unresolved references, and advisory prose concerns so the owner can correct the artifact.
Sicherheitsaudit
SicherAll 254 static matches are false positives in their reviewed context. They are documentation literals, schema identifiers, parser patterns, or local validation references; no command execution, network request, secret access, destructive file operation, or encoded payload was evidenced. No prompt-injection or data-exfiltration intent was found.
Risikofaktoren
⚙️ Externe Befehle (50)
🔑 Umgebungsvariablen (2)
🌐 Netzwerkzugriff (21)
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/theislampill-stow/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/theislampill-stow?utm_source=security_passport_badge)HTML-Badge
<a href="https://skillstore.io/skills/theislampill-stow?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/theislampill-stow/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Einbettungskarte
<iframe src="https://skillstore.io/embed/skills/theislampill-stow.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
theislampill. (2026). stow security audit report (audit version 1) [Author version 0.4.2]. Skillstore. https://skillstore.io/skills/theislampill-stow/audits/1BibTeX-Zitat
@techreport{theislampill-theislampill-stow-2026,
author = {theislampill},
title = {stow security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/theislampill-stow/audits/1},
note = {Author version 0.4.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "stow security audit report (audit version 1)"
version: "0.4.2"
type: report
authors:
- name: "theislampill"
date-released: "2026-09-06"
url: "https://skillstore.io/skills/theislampill-stow/audits/1"
identifiers:
- type: other
value: "skillstore:theislampill-stow:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
Polish technical documentation
Rewrite a README or public technical document for direct structure, precise claims, consistent terminology, and preserved command examples.
Prepare operational procedures
Shape runbooks, plans, audits, and handoffs into bounded steps with visible evidence, limitations, verification, and rollback details.
Validate structured deliverables
Check JSON, JSONL, YAML, or Markdown artifacts against their contracts while retaining literal values and reporting structural defects.
Diese Prompts ausprobieren
Rewrite this README for direct technical clarity. Preserve every command, path, identifier, quotation, and data value. Return only the revised README.
Review this runbook for missing preconditions, unclear actions, unsupported claims, and absent verification or rollback details. List concrete corrections and preserve all commands exactly.
Validate this JSON, JSONL, YAML, or Markdown artifact against the stated contract. Report parse and structural issues, distinguish warnings from failures, and do not rewrite protected values.
Apply STOW to this technical document. Classify each region, identify the active profile and relevant rule conflicts, preserve protected literals, and return the smallest complete set of corrections with evidence.
Bewährte Praktiken
- State the output contract and protected literals before requesting a rewrite.
- Provide authoritative sources for claims, numbers, terminology, and required formats.
- Use the named validator on the actual final artifact when the format has a supported schema.
Vermeiden
- Do not ask STOW to invent commands, evidence, versions, citations, or current system state.
- Do not treat advisory prose findings as proof of a security, correctness, or authorship defect.
- Do not label editable text as protected when the requested change requires literal editing.
Häufig gestellte Fragen
What is STOW?
Which tools support STOW?
What content can STOW review?
Does STOW change commands or paths?
Are prose lint results blocking?
Can STOW validate schemas?
Entwicklerdetails
Autor
theislampillLizenz
LICENSE
Autorenversion
v0.4.2
Skillstore-Revision
r1
Repository
https://github.com/theislampill/stow/tree/bab13dbd8bd83cfc8cc72b7f64761e668302ff6e/skills/stowRef.
e5464e662405de6361fdde6b984f9ea865635f64
Aktualität der Wartung
8.9.2026
Nutzung
1 Downloads · 0 Aufrufe
Dateistruktur
📁 corpus/
📄 rules.md
📁 style/
📁 verbs/
📁 words/
📄 usage.md
📄 LICENSE
📄 activation-and-precedence.md
📄 controlled-technical-writing.md
📄 cross-harness-interchange.md
📁 rules/
📄 controlled-dictionary-v1.json.gz
📄 controlled-dictionary.schema.json
📄 project-terminology.schema.json
📁 runtime/
📁 schemas/
📄 SKILL.md
📄 AUDIT.md
📄 PLAN.md
📄 STATE.md