Brain knowledge base operations. The core read/write cycle: brain-first lookup, read-enrich-write loop, source attribution, ambient enrichment, back-linking. Read this before any brain interaction.
Academic paper reading system — find papers via Semantic Scholar, read with structured notes, discuss with auto-recording, track progress. 7 commands: /setup /feed /read /discuss /recap /update /sync
Use when an agent needs to operate the bgm CLI as a user-facing Bangumi tool: auth checks, profile reads, subject and group lookup, collection reads or writes, group topic reads or writes, Turnstile-gated mutations, JSON output, and other ordinary non-TUI commands. Do not use this when editing the bgm-cli codebase itself.
Use this skill to execute a shaped Package within a build session. Implements the full building process: orient on the codebase, pick a first piece (core/small/novel), integrate vertically with TDD, discover and map scopes, track progress with hill charts, and scope hammer when capacity runs low. For web projects, verifies with browser automation. Writes handover documents for multi-session continuity. Only use after a Package has Shape Go approval. Use when the user says "/build NNN" or "let's build feature NNN" or "start building NNN". --- # Shape Up: Build You are running a **Build session** — the execution phase of the Shape Up methodology. Building turns a shaped Package into deployed software within a fixed appetite. > **Reference Index** — Read only what you need, when you need it. > > | File | Contains | When to read | > |------|----------|-------------| > | `references/02-building-process.md` | Full building methodology: orientation, vertical integration, scopes, shipping | **Read now** — core to this skill | > | `references/05-hill-chart-protocol.md` | Hill chart model, uphill/downhill phases, stuck scope protocol | **Read now** — needed for progress tracking | > | `references/04-scope-hammering-rules.md` | Scope cutting decision framework, must-have vs nice-to-have | **Read at Step 6** when capacity gets tight | > | `references/07-pitfalls.md` | Three critical failure modes | Read if scopes are stuck or work feels undershaped | > | `references/00-glossary.md` | Shape Up terminology definitions | Read if you encounter an unfamiliar term | > | `references/01-shaping-process.md` | How shaping works | Read if the Package seems incomplete or unclear | > | `references/03-pitch-template.md` | Package format (5 ingredients) | Read if you need to interpret the Package structure | > | `references/06-agent-workflow-guide.md` | Full pipeline overview, agent decision rules | Read if reactive work conflicts with build | > | `references/08-framing.md` | Framing methodol
Read and summarize arXiv papers from title. Use when the user asks to read/understand an arXiv paper, provides a paper title, or mentions downloading arXiv TeX source (arxiv.org/src). Fetch paper metadata, download and extract source, locate main .tex, read the full paper, and write structured Chinese notes to arxiv_paper_notes using {paper_id}_{method}.md.
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:
