- 📄 SKILL.md
commit
Validated commit — runs quick checks before committing. Use when ready to commit changes.
Validated commit — runs quick checks before committing. Use when ready to commit changes.
平台向长篇网文连载写作助手。负责新项目立项、章节续写、单章返修、项目记忆维护、长篇分卷治理和章节质检。内置章节/场景/语言三层写法原则,适配爽文、言情、权谋等主流题材,支持从脑洞到超长篇全流程。更多信息关注抖音君黎。
Address PR review comments systematically. Use when responding to code review feedback on a pull request.
Generates a CSS stylesheet for a lobster.js page, targeting lbs-* class names. Use this whenever the user wants to style a lobster.js page, create a CSS theme for lobster.js, customize the visual appearance of a lobster.js site, or asks for CSS that targets lbs-* classes. Also trigger when a user describes a visual style (e.g. "dark mode", "minimal", "playful") while working on a lobster.js project — even if they don't mention CSS or lbs-* explicitly. --- Generate a CSS stylesheet for a lobster.js page based on the user's design description. lobster.js outputs semantic HTML where every element has a predictable `lbs-*` class name. Write CSS targeting these classes to style the page. Use the design description from the user's message. If no description is given, generate a clean minimal light theme. --- ## HTML structure reference ```html <!-- Content wrapper --> <div id="content"> … </div> <!-- Page regions --> <header class="lbs-header"> … </header> <footer class="lbs-footer"> … </footer> <!-- Headings --> <h1 class="lbs-heading-1"> … </h1> <h2 class="lbs-heading-2"> … </h2> <!-- h3–h6 follow the same pattern --> <!-- Paragraph --> <p class="lbs-paragraph"> … </p> <!-- Inline --> <em class="lbs-emphasis"> … </em> <strong class="lbs-strong"> … </strong> <del class="lbs-strikethrough"> … </del> <code class="lbs-code-span"> … </code> <!-- Horizontal rule --> <hr class="lbs-hr" /> <!-- Code block --> <div class="lbs-code-block"> <div class="lbs-code-filename">filename.js</div> <!-- optional --> <pre data-language="js"><code class="language-js"> … </code></pre> </div> <!-- Blockquote --> <blockquote class="lbs-blockquote"> <p class="lbs-paragraph"> … </p> </blockquote> <!-- Lists --> <ul class="lbs-ul"> <li class="lbs-list-item"> … </li> </ul> <ol class="lbs-ol"> <li class="lbs-list-item"> <input type="checkbox" class="lbs-checkbox" /> … <!-- task list --> </li> </ol> <!-- Table (standard) --> <table class="lbs-table"> <thead><tr><th> … </th></tr></thead> <tbody><tr><
**MANDATORY** for Delphi/Pascal symbol lookup. Use delphi-lookup.exe FIRST (before Grep/Glob) when:
Lightpanda browser, drop-in replacement for Chrome and Openclaw default browser - faster and lighter for tasks without graphical rendering like data retrieval. Use it via MCP server, CLI fetch, or CDP with Playwright/Puppeteer.
Test TUI (Text User Interface) applications using tmux. Use this skill when you need to automate testing of terminal-based applications by sending keystrokes and capturing pane output.
Install, deploy, or reconfigure a VibeBridge Main server. Use when setting up configs/main.toml, asking the user for required main deployment settings, creating a dedicated Python virtualenv, deciding whether to rebuild the frontend, choosing nohup/systemd/launchd/manual process management, and validating the Main health endpoint plus browser entrypoint. 适用于安装或部署 VibeBridge Main 服务,并在改配置前向用户确认必要参数。
Trading skill for executing live agent trades on Lighter (crypto perps) and Hyperliquid (HIP3 stocks). Use when user asks about trading, positions, signals, executing trades, live agent mode, cycle files, or managing EVClaw operations. Supports (1) Running live agent cycles via /live-agent, (2) Executing manual trades via /trade and /execute, (3) Viewing signals/positions, (4) Managing trading configuration, (5) Understanding signal types and decision logic, (6) Agent-driven incident response and triage.
Git decorator that gives every commit memory — links AI sessions, tokens, and code attribution to your commits. Use when the user asks about commit history with AI context, session history, code attribution, token usage, or generating a developer card.
Interactive setup wizard for configuring any repository with Claude Code best practices. Use when user says "setup claude", "init claude", "configure claude code", "setup repository", "boris setup", "best practices setup", or wants to configure their repo for optimal AI-assisted development.
Local Python orchestration skill: multi-agent workflows via shared blackboard file, permission gating, token budget scripts, and persistent project context. The bundled Python scripts make no network calls and have zero third-party dependencies. Workflow delegations via the host platform's sessions_send may invoke external model APIs.
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: