Borrowing it
Nothing to install: this file belongs to ryan-yuuu/crypto-trading-arena. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ryan-yuuu/crypto-trading-arena/main/.agents/skills/diataxis-docs-writer/SKILL.mdgit clone --depth 1 https://github.com/ryan-yuuu/crypto-trading-arenaWrote 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/ryan-yuuu/crypto-trading-arena/diataxis-docs-writer)<a href="https://agentmods.dev/skills/ryan-yuuu/crypto-trading-arena/diataxis-docs-writer"><img src="https://agentmods.dev/badge/skills/ryan-yuuu/crypto-trading-arena/diataxis-docs-writer/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/ryan-yuuu/crypto-trading-arena/diataxis-docs-writer"><img src="https://agentmods.dev/badge/skills/ryan-yuuu/crypto-trading-arena/diataxis-docs-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00218 | $0.02700 |
| Opus 5 | $0.00109 | $0.01350 |
| Sonnet 5 | $0.00044 | $0.00540 |
| Haiku 4.5 | $0.00022 | $0.00270 |
Grade A, and why
diataxis-docs-writer scanned grade A with 0 findings 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 11d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to diataxis-docs-writer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diátaxis documentation
Good documentation is not one thing. It is four things, each answering a different question a user has, each written in a different way. Most bad documentation is bad not because the writing is poor but because two of these four got mixed together — a tutorial clogged with explanation, a reference page that wanders into opinion, a "how-to" that's really a half-finished lesson.
Your job with this skill is to keep them separate. Decide which kind you're writing, commit to its discipline, and link out to the others rather than bleeding into them.
Diátaxis is a guide, not a plan. You don't start by building four empty sections and filling them in. You write each piece well, in its proper mode, and good structure emerges from that.
The two axes (why there are exactly four)
Every craft involves two distinctions. Documentation must serve both sides of each:
- Action ↔ Cognition — is the content about doing (practical steps) or about knowing (theoretical facts and ideas)?
- Acquisition ↔ Application — does it serve the user at study (learning the craft) or at work (applying it to get something done)?
Cross those two axes and you get four quadrants — the four documentation types. There can't be three or five; the two axes define the whole territory.
Step 1 — Classify before you write (the compass)
Before writing a sentence, decide which type you're producing. Ask just two questions:
- Action or cognition? (Is this about what the user does, or what they know?)
- Acquisition or application? (Is the user studying, or working?)
| If the content informs… | …and serves the user's… | …then it is a… | It answers | Its form is |
|---|---|---|---|---|
| action | acquisition (study) | Tutorial | "Can you teach me to…?" | a lesson |
| action | application (work) | How-to guide | "How do I…?" | a recipe |
| cognition | application (work) | Reference | "What is…? / What are the options?" | dry description |
| cognition | acquisition (study) | Explanation | "Why…? / Tell me about…" | a discursive article |
What ships with it
7 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.
- 11d ago First seen · 196 lines · 218 tokens per session scan A 67190e949979
diataxis-docs-writer is a skill published in the GitHub repository ryan-yuuu/crypto-trading-arena (126 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 218 tokens to every session and 2,700 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to diataxis-docs-writer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
horus-flow-mcp
If the user asks you to write a trading bot, an algorithmic trading script, or requests any market analysis (Crypto/US Equities).
backtest-interpretation
Interpret backtest output from the historicalpriceanalyzer tool — four built-in strategies (SMA crossover, RSI reversal, breakout, mean reversion) over Indian stocks, with Sharpe, max drawdown, win rate, and avg trade. Use when the user asks about "backtest", "how would strategy X have performed", "test this on…
tax-harvest
Walk an Indian retail trader through tax-loss harvesting on their Zerodha equity holdings — identify STCG/LTCG positions with losses, estimate tax savings under Indian capital-gains rules, and plan the sell-and-rebuy sequence while avoiding wash-sale equivalents. Use when the user asks about "tax harvesting", "tax…
sector-rotation
Analyze sector exposure in an Indian equity portfolio — which sectors the user is overweight/underweight vs NIFTY benchmarks, how yesterday's FII/DII flows align with current holdings, and what the concentration numbers actually say. Use when the user asks about "sector exposure", "sector rotation", "am I too…
trade-check
Run a pre-flight check before placing an equity order on Zerodha Kite — current price, margin required, portfolio concentration impact, existing exposure, and stop-loss suggestion. Use when the user says "should I buy X", "pre-trade check on Y", "can I afford Z quantity of ABC", "check before I place order", or asks…
eod-review
End-of-day trading review for an Indian retail trader on Zerodha Kite — day P&L, positions still open, orders placed today, alert activity, MIS square-off warnings, and action items for tomorrow. Use when the user says "EOD review", "end of day summary", "how did today go", "close the books", "wrap up trading day", or…