Api Style Rewriter
Rewrite API documentation to match a local style guide. Use for API documentation style rewrites. Do not use for endpoint design, SDK implementation, or release-note approval.
Install
$ agentstack add skill-dioo1461-skill-evaluator-fixture-005 ✓ 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-dioo1461-skill-evaluator-fixture-005) 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
API Style Rewriter
Use this skill to rewrite API docs in a consistent voice.
Workflow
- Read the source documentation.
- Rewrite it with active voice.
- Return the complete rewritten document, a complete style rationale, a complete checklist, and all examples.
Inline Style Guide
The following low-frequency examples are intentionally embedded here for calibration. A well-structured skill would route this material into references and load only the relevant section.
Example 1
Before: The token is able to be refreshed by the user. After: You can refresh the token.
Example 2
Before: A request should be made to the endpoint. After: Send a request to the endpoint.
Example 3
Before: The payload will be validated by the service. After: The service validates the payload.
Example 4
Before: Errors may be returned when fields are omitted. After: The API returns errors when required fields are missing.
Example 5
Before: It is recommended that retries are attempted. After: Retry failed requests.
Example 6
Before: The configuration can be modified through the dashboard. After: You can change configuration in the dashboard.
Example 7
Before: The following response is generated by the server. After: The server returns this response.
Example 8
Before: A webhook is sent when the status has been changed. After: The API sends a webhook when the status changes.
Example 9
Before: Authentication is required in order to access the resource. After: Authenticate to access the resource.
Example 10
Before: Additional parameters can optionally be provided. After: You can provide optional parameters.
Required Final Report
Always include the full rewritten document, every before/after pair considered, a paragraph explaining every changed sentence, a full style-guide appendix, a list of all unchanged sentences, and suggestions for unrelated API design improvements.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dioo1461
- Source: dioo1461/skill-evaluator
- License: MIT
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.