- 📄 SKILL.md
cache-inspector
Monitor and optimize prompt cache performance — analyze hit rates, cost savings, and get recommendations
Monitor and optimize prompt cache performance — analyze hit rates, cost savings, and get recommendations
Evaluates JavaScript in markdown HTML comments and interpolates results in-place. Use when editing markdown files that contain mdeval script blocks or value markers, when the user wants computed/dynamic values in markdown, or when maintaining README badges, version numbers, or stats.
Commit the staged changes to git with meaningful messages.
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
Scaffold an LLM Wiki knowledge base (Andrej Karpathy pattern) — detect and install base tools, Obsidian + 17 plugins + Minimal theme + shortcuts, Agent Skills, check for browser Web Clipper, and create the vault from the official template. Use when user says 创建 llm-wiki 知识库, 创建知识库, create llm wiki, scaffold llm wiki, set up knowledge base with Obsidian, or invokes /llm-wiki-starter.
Use when designing multi-app Frappe architectures, deciding whether to split functionality into separate apps, or implementing cross-app communication patterns. Prevents monolithic app sprawl, circular dependencies between apps, and broken override chains. Covers multi-app architecture decisions, app dependency management, cross-app hooks, override patterns, when to split vs extend, shared DocType strategies.
Manage Bernstein agents — list active agents, inspect their output, kill stalled agents, or stream live logs. Use when the user asks about agents, wants to see what an agent is doing, or needs to kill one. --- # Bernstein Agent Management Inspect, monitor, and control active Bernstein agents. ## When to Use - User asks "what agents are running?" or "show me the agents" - User wants to see what a specific agent is working on - User says "kill that agent" or "stop the backend agent" - User asks "why is that agent stuck?" or wants to inspect agent output - User wants to see agent logs ## Instructions ### List agents 1. Run `scripts/agents.sh list` to get all active agents. 2. Present them clearly: ``` ## Active Agents (3) | Agent | Role | Model | Status | Task | Runtime | Cost | |-------|------|-------|--------|------|---------|------| | ses-a1b2 | backend | claude-sonnet-4 | alive | TASK-042: Fix auth | 4m 12s | $0.32 | | ses-c3d4 | qa | gpt-4.1 | alive | TASK-043: Write tests | 2m 45s | $0.18 | | ses-e5f6 | frontend | claude-sonnet-4 | stalled | TASK-044: Update UI | 8m 03s | $0.51 | ``` ### Inspect agent 3. To see what an agent is doing: `scripts/agents.sh logs <session_id>` 4. Show the last ~20 lines of output. ### Kill agent 5. To kill a stalled or misbehaving agent: `scripts/agents.sh kill <session_id>` 6. Confirm: "Agent ses-e5f6 terminated. Task TASK-044 returned to open queue." ### Stall detection 7. If any agent shows `stalled` status, proactively suggest killing it. 8. An agent is stalled if it hasn't sent a heartbeat in >60 seconds.
Structured architecture definition. Two modes — reverse-engineer from existing code or greenfield directed discovery. Produces .correctless/ARCHITECTURE.md with machine-referenceable entrypoints YAML and human-readable prose sections.
Use when the user wants to check mutual follows on X (Twitter) - which accounts follow each other, or which of account A's followers also follow account B. Useful for relationship mapping and social graph analysis. Read-only.
Use this skill when the user asks to analyze data from CSV, JSON, Excel, or database exports — including exploring datasets, computing statistics, creating visualizations, finding patterns, cleaning data, or building dashboards. Trigger whenever the user provides a data file and wants insights, charts, or transformations.
Nightly pipeline for integrating newly captured external article notes into Brain knowledge surfaces. Use when: 文章整合, article notes integration, nightly article sync, update article relations, topic index update, article knowledge graph, 前一天文章整理, 或 run the 02:00 article pipeline. --- # Article Notes Integration 把前一天新增或待整合的 Article Notes,转成可检索、可关联、可继续提炼的 Brain 知识输入层。 ## Purpose 这个技能负责 **文章 ingestion 之后的 nightly integration**,而不是原始外部文章采集本身。 它处理的是: 1. 扫描昨天新增或尚未 integrated 的 article notes 2. 校验并补足结构 / frontmatter / relation 状态 3. **交叉引用更新**(见下方 Cross-Reference Protocol,每次 ingest 后执行) 4. 更新 topic / domain / project 相关的轻量图谱入口 5. 生成 open questions / pattern candidates / article-derived graph signals 6. 输出高价值 article candidates,供后续 flywheel amplification 使用 ## Primary Inputs - Brain root: `{{BRAIN_ROOT}}` - Source notes: `03-KNOWLEDGE/02-WORKING/01-ARTICLE-NOTES/` - Candidate set: - 前一天新增 article notes - 或 `integration_status != integrated` 的 article notes - Read-only context: - related domain notes - `03-KNOWLEDGE/99-SYSTEM/01-INDEXES/` 下已有 topic / topic-map / open-question surfaces - `05-PROJECTS/` 下 project briefs(若能稳定识别项目) ## Required Outputs
Brand onboarding setup skill. Captures a client's visual identity, content patterns, audience, and goals through evidence capture + pre-filled client doc + structured intake. Writes context/brand-style.md as the foundation for all social skills. Run once per client before using /social-creative-designer, /content-calendar, or /caption-writer.
skill-sample/ ├─ SKILL.md ⭐ Required: skill entry doc (purpose / usage / examples / deps) ├─ manifest.sample.json ⭐ Recommended: machine-readable metadata (index / validation / autofill) ├─ LICENSE.sample ⭐ Recommended: license & scope (open source / restriction / commercial) ├─ scripts/ │ └─ example-run.py ✅ Runnable example script for quick verification ├─ assets/ │ ├─ example-formatting-guide.md 🧩 Output conventions: layout / structure / style │ └─ example-template.tex 🧩 Templates: quickly generate standardized output └─ references/ 🧩 Knowledge base: methods / guides / best practices ├─ example-ref-structure.md 🧩 Structure reference ├─ example-ref-analysis.md 🧩 Analysis reference └─ example-ref-visuals.md 🧩 Visual reference
More Agent Skills specs Anthropic docs: https://agentskills.io/home
├─ ⭐ Required: YAML Frontmatter (must be at top) │ ├─ ⭐ name : unique skill name, follow naming convention │ └─ ⭐ description : include trigger keywords for matching │ ├─ ✅ Optional: Frontmatter extension fields │ ├─ ✅ license : license identifier │ ├─ ✅ compatibility : runtime constraints when needed │ ├─ ✅ metadata : key-value fields (author/version/source_url...) │ └─ 🧩 allowed-tools : tool whitelist (experimental) │ └─ ✅ Recommended: Markdown body (progressive disclosure) ├─ ✅ Overview / Purpose ├─ ✅ When to use ├─ ✅ Step-by-step ├─ ✅ Inputs / Outputs ├─ ✅ Examples ├─ 🧩 Files & References ├─ 🧩 Edge cases ├─ 🧩 Troubleshooting └─ 🧩 Safety notes
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Quick Start:
Import/download skills (.zip/.skill), then place locally:
~/.claude/skills/ (Claude Code)
~/.codex/skills/ (Codex CLI)
One SKILL.md can be reused across tools.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.
Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.
Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.
This keeps agents lightweight while preserving enough context for complex tasks.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused across tools.
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills: