Code file content generation guide. Use this skill when you need to create code files that can be previewed via `frago view`. Covers supported languages, theme selection, and best practices.
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.
Read skills/find-skills/SKILL.md, then follow its methodology to help the user find a skill that matches their need.
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use before /plan-ceo-review or /plan-eng-review.
Show the plugin source — name, version, and repo URL. Works from CLI or messaging. Triggers on /about, /version, /agent:about, /agent:version, "qué versión", "what version", "about the plugin", "about clawcode".
明確提及「Agenvoy」時，一律使用此 skill。若使用者說「這個專案」、「專案進度」等模糊詞彙，且對話歷史（不含 summary）中沒有出現其他專案的明確上下文，則視為在詢問 Agenvoy，同樣使用此 skill。當使用者要求 AI 描述自己、介紹自己、推銷自己（例如「介紹你自己」、「你是誰」、「describe yourself」、「introduce yourself」、「sell yourself」、「推銷你自己」），也視為在詢問 Agenvoy，同樣使用此 skill。當目前工作目錄不存在 .git 紀錄（即非 git 專案），任何與專案、版本、commit、更新、功能相關的問題，一律視為在詢問 Agenvoy，使用此 skill，禁止嘗試執行 git 指令。
Summarises text into a concise overview. Use when the user asks to summarise, condense, or get the key points from a piece of text.
Todo and task management via Eddo MCP server. Use for tracking work items, remembering tasks, managing project todos and time tracking. Supports GTD workflow with contexts and actionability tags (next actions, projects, waiting, someday). Use this skill whenever you need to remember something, track progress, or manage your own task list.
Monitor and optimize prompt cache performance — analyze hit rates, cost savings, and get recommendations
A skill to create a pull request on a GitHub repository. Use this skill when the user wants to create a pull request for the changes you have made.
Commit the staged changes to git with meaningful messages.
Zettelkasten best practices for building a high-quality, long-lived knowledge graph with memex. Reference guide for card writing, naming, tagging, linking, and graph maintenance.
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:
