tech data playbook

Name: tech data playbook
Author: LeoYeAI

by LeoYeAI·2mo ago

World-Class Technology & Data Playbook. Use for: software development best practices, IT infrastructure design, cyberse…

Developer DocsClaude CodeMedium risk · 中风险open source · 开源

Before you install安装前须知

!Accesses the network会访问网络

Editor's verdict· 编辑结论

World-Class Technology & Data Playbook. Use for: software development best practices, IT infrastructure design, cybersecurity strategy, data analytics, business intelligence, automation & DevOps, cloud computing architecture, AI/ML adoption, technical architecture decisions, dig…
— Editorial team · 编辑团队

Install via Skills CLI

Use npx skills add to install this skill into the selected agent. Phase 0 commands are generated from source rules, not verified.

Codex

npx skills add https://github.com/LeoYeAI/openclaw-master-skills/blob/main/skills/tech-data-playbook/SKILL.md -g -a codex -y

Drop `-g` to install project-locally

✓

Best for适合什么场景

数据分析
科研计算
表格处理

✗

Not for不适合什么场景

Workflows that require stronger human review than this catalog entry documents.需要比当前目录条目更严格人工复核的工作流。

vs alternativesvs 其他选择

Full compare table完整对比表 →

#1Anthropic Doc Coauthoring

Guide a doc from raw context to reader-tested clarity.

★ 4.7·163k stars

diff · 差异Best for long-lived documents that real readers have to act on — RFCs, design docs, architecture write-ups, technical specs. Built around a reader-test loop: draft, hand to a fresh reader, see if they can answer the document's own questions, revise. Anthropic-authored, so the format and review conventions match how Claude actually consumes context. Not for one-pagers or release notes — release-briefing handles those with much less ceremony.

#2Docs Release

Sync the docs after the code changes, not three weeks later.

★ 4.7·9.3k stars

diff · 差异Best for the docs that age worst — README, ARCHITECTURE, getting-started — when code has moved on and prose hasn't. Reads the diff, finds the docs that reference the changed code path, and proposes the smallest update needed to keep them honest. Strongest after architectural refactors or API rename waves; weakest on net-new documentation. For full authoring loops with reader testing, anthropic-doc-coauthoring is the better fit.

#3DX Audit

Measure the onboarding pain your docs politely hide.

★ 4.5·5.4k stars

diff · 差异Best when you need to know how new users actually experience your product, not how your team thinks they do. Walks the public onboarding path — docs, install, first API call, first error message — and times each step. Catches the silent failures: docs promising a feature that doesn't exist yet, paste-this commands that don't run on macOS, default settings that 404. Strongest before a developer-facing launch. Skip it for internal-only tooling — that's not what it's tuned for.

Side-by-side compare维度对比

Key differences with same-lane alternatives

	this skill · 当前tech data playbook	Anthropic Doc Coauthoring	Docs Release	DX Audit
Rating · 评分	—	4.7	4.7	4.5
Stars · 星标	2.0k	163k	9.3k	5.4k
Risk · 风险	Medium risk · 中风险	Low risk · 低风险	Low risk · 低风险	Low risk · 低风险
Best for · 最适合	数据分析	Guide a doc from raw context to reader-tested clarity.	README updates	Measure the onboarding pain your docs politely hide.
Not for · 不适合	Workflows that require stronger human review than this catalog entry documents.	Workflows that require stronger human review than this catalog entry documents.	Live deploy verification	Workflows that require stronger human review than this catalog entry documents.

Audit notes审计备注

not individually audited · 未独立审计

Source源码open on GitHub · 公开✓

Author作者community · 社区!

Network网络访问not individually audited · 未独立审计!

Filesystem文件写入not individually audited · 未独立审计!

Dependencies依赖not individually audited · 未独立审计!

Telemetry遥测none · 无✓