Stip Docs
Create or update documentation affected by a checked change, grounded in the implementation and intended readers.
Install
$ agentstack add skill-bryann2k-stipulate-skills-stip-docs ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-bryann2k-stipulate-skills-stip-docs) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
stip-docs
Begin after stip-check. Inspect current docs and identify affected readers: users, maintainers or operators. Update the smallest complete documentation set: usage, changed API/config behavior, examples, migration or runbook where applicable. Avoid generating empty documents or a universal docs package.
Use selected extension docs references when relevant. Verify examples and claims against actual behavior. Documentation should be usable outside this conversation and distinguish supported behavior from limitations.
After Markdown, reStructuredText or text edits, run docs --paths --summary . This accepts declared text-document changes while requiring the checked source tree to remain unchanged. For MDX, generated documentation or executable documentation code, rerun stip-check after those edits, then run docs with a summary. If no documentation changes are needed, explain that specifically in the summary.
Do not mark documentation complete if required reader needs remain unmet. Do not classify code changes as documentation to avoid verification. The next step is stip-archive.
Runtime
Use the Python runtime bundled with this skill, independent of the current directory:
python3 /scripts/workflow.py --root Python 3.10+ and Git are required for implementation and archive. Run --help or --help for exact arguments. The runtime is offline and never installs tools. System/developer instructions, current user intent and environment permissions remain authoritative.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: BRYANN2K
- Source: BRYANN2K/stipulate-skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.