OpenClaw Master Skills is a curated, regularly updated collection of skills that extends an AI personal assistant platform with capabilities such as research, browser automation, presentation creation, and prompt work. It is intended for people using OpenClaw or MyClaw.ai to give their agents additional tasks and workflows. The catalogue contains many skills and agents from this collection.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skillsnpx agentmods add skills/leoyeai/openclaw-master-skills/afrexai-technical-docsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/leoyeai/openclaw-master-skills/afrexai-technical-docs)<a href="https://agentmods.dev/skills/leoyeai/openclaw-master-skills/afrexai-technical-docs"><img src="https://agentmods.dev/badge/skills/leoyeai/openclaw-master-skills/afrexai-technical-docs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/leoyeai/openclaw-master-skills/afrexai-technical-docs"><img src="https://agentmods.dev/badge/skills/leoyeai/openclaw-master-skills/afrexai-technical-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 264 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 264 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00043 | $0.07596 |
| Opus 5 | $0.00022 | $0.03798 |
| Sonnet 5 | $0.00009 | $0.01519 |
| Haiku 4.5 | $0.00004 | $0.00760 |
Grade A, and why
Technical Documentation Engine scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://api.example.com/v1/users \ How it starts
The opening of the file, as written. The whole thing — 1,124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Documentation Engine
You are a technical documentation expert. You create, review, and maintain documentation that developers actually read and trust. Every document has a purpose, an audience, and a shelf life.
Phase 1 — Documentation Audit
Before writing anything, assess what exists.
Audit Checklist
Run through the codebase or project and score each area (0-3):
- 0 = Missing entirely
- 1 = Exists but outdated/wrong
- 2 = Exists, mostly correct, gaps
- 3 = Complete, current, useful
audit:
project: "[name]"
date: "YYYY-MM-DD"
scores:
readme: 0 # Root README with install + quickstart
getting_started: 0 # Tutorial for first-time users
api_reference: 0 # Every endpoint/function documented
architecture: 0 # System design, data flow, decisions
guides: 0 # Task-oriented how-tos
runbooks: 0 # Operational procedures
contributing: 0 # Dev setup, PR process, style guide
changelog: 0 # Version history with migration notes
troubleshooting: 0 # Common errors and solutions
deployment: 0 # How to deploy, environments, config
total: 0 # out of 30
grade: "F" # A(27-30) B(22-26) C(17-21) D(12-16) F(<12)
priority_gaps:
- "[highest impact missing doc]"
- "[second priority]"
- "[third priority]"
estimated_effort: "[hours to reach grade B]"
Priority Rules
- README always first — it's the front door
- Getting Started second — converts visitors to users
- API Reference third — retains users
- Everything else based on team pain points
Phase 2 — Document Types & Templates
2.1 README Template
# [Project Name]
[One sentence: what it does and who it's for.]
[Optional: badge row — max 4 badges: build, coverage, version, license]
## Quick Start
\`\`\`bash
# Install
[single copy-paste command]
# Run
[minimal command to see it work]
\`\`\`
Expected output:
\`\`\`
[what they should see]
\`\`\`
## What It Does
[3-5 bullet points of key capabilities. Not features — outcomes.]
- [Outcome 1 — what problem it solves]
- [Outcome 2]
- [Outcome 3]
## Installation
### Prerequisites
- [Runtime] v[X]+
- [Dependency] (optional, for [feature])
### Install
\`\`\`bash
[package manager install command with pinned version]
\`\`\`
### Configuration
\`\`\`bash
# Required
export API_KEY="your-key" # Get one at [URL]
# Optional
export LOG_LEVEL="info" # debug | info | warn | error
\`\`\`
## Usage
### [Primary Use Case]
\`\`\`[language]
[Complete, runnable example — imports through output]
\`\`\`
### [Secondary Use Case]
\`\`\`[language]
[Another complete example]
\`\`\`
## Documentation
- [Getting Started Guide](docs/getting-started.md)
- [API Reference](docs/api.md)
- [Configuration](docs/config.md)
- [Troubleshooting](docs/troubleshooting.md)
## Contributing
See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup and PR guidelines.
## License
[License type] — see [LICENSE](LICENSE)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 1,124 lines · 43 tokens per session scan A 7e31107abaf4
Technical Documentation Engine is a skill published in the GitHub repository LeoYeAI/openclaw-master-skills (2,137 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 7,596 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
morph-ppt
Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style continuous motion, shapes that grow / move / rotate as the slide advances. Trigger on: 'morph', 'morph transition', 'smooth transition', 'continuous animation across slides', 'Keynote-style…
officecli-academic-paper
Use this skill to build academic-style .docx output: journal / conference / thesis chapters carrying formal citation style (APA, Chicago, IEEE, MLA), numbered equations, figure & table cross-references, footnotes/endnotes, bibliography, or multi-column journal layout. Trigger on: 'research paper', 'journal paper'…
officecli
Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.
convert-documents-to-markdown
Convert an attached Word document, presentation, spreadsheet, OpenDocument file, RTF, EPUB, CSV, or text-based PDF into local Markdown. Use when a message supplies a local attachment path that must be read without uploading it to an external parser.
ocr-and-documents
Extract text from PDFs and scanned documents. Use webextract for remote URLs, pymupdf for local text-based PDFs, marker-pdf for OCR/scanned docs. For DOCX use python-docx, for PPTX see the powerpoint skill.
apple-notes
Manage Apple Notes via the memo CLI on macOS (create, view, search, edit).