Explore skills

通过 CLI 查询 Datadata — 运行临时 SQL、检查数据源元数据、列表和描述表、下载 NDJSON/CSV 格式结果。当用户提到 Datadata、想查询数据、探索数据源或表 schema、获取查询结果时使用此 skill。触发：Datadata、数据探索、SQL查询、表检查、执行结果。

Audits and cleans up Claude Code auto-saved memory files. Scores on 4 dimensions, detects conflicts, opens a visual dashboard. Trigger on: memories, memory quality, memory cleanup, memory health, memory dashboard, 检查记忆, 清理记忆, 记忆质量, 记忆看板.

为 Datadata 平台编写 DQL 数据处理脚本 — 基于 Starlark 的扩展脚本语言，支持 DataFrame/Series 操作、SQL 查询、HTTP 请求等。当用户需要编写数据转换、数据清洗、数据生成或自定义数据处理逻辑时使用此 skill。

Fire-and-forget async Codex delegation. This skill should be used when delegating debugging, implementation, refactoring, or code review to OpenAI Codex without blocking the current conversation. Trigger when: (1) implementation or refactoring touching 3+ files — do not attempt yourself, delegate, (2) debugging after 1-2 failed root-cause attempts — stop spinning and hand it off, (3) user says 'de

Archived. The active Obsidian skills now reside in claude-code-skills under productivity.

Transform raw/crude document drafts into structured content. Use when a document is a skeleton of ideas, notes, or stream-of-consciousness that needs generative expansion rather than review polish.

Generates physical world foundations: biomes, planetary systems, climate, and ecological zones with embedded narrative tension. Use when creating a new world, planet, biome, or ecosystem, or when user says "new world", "new planet", "new biome", "build a world", "create a setting", or "environmental design". Does NOT write final files — use /writing-worldbuilding for that.

Search indexed documents (PDF, Word, Excel, PPT, TXT) using BM25 keyword search. Use for EDA tools, company docs, bug reports, and technical documentation.

Read-and-revise pass for any drafted post. Applies writing-style.md checklist, tightens prose, kills filler. Run after drafting and before ai-slop-check.

Post-launch breakdown (~800-1500 words). What you shipped, the numbers (good or bad), what worked, what didn't, what you'd change next time. Use after every product/launch/release where you have real numbers to share — including (especially) when the numbers are embarrassing.

Vision/strategy piece (~1500-3000 words). Rare format — once or twice a year. Names what you're building, why it matters, and how you'll get there. Use to plant a flag, reset direction, or invite people into a longer-term mission.

On-demand write protection for approved files during final assembly, implemented via Claude Code PreToolUse hooks — a rare working example of hook-based file guards. Use when the user enters a final-assembly phase, wants to freeze approved work, or says "lock scenes", "protect these files", "freeze approved", "/lockscenes", "add a write guard", or asks how to temporarily block edits during a criti