███████╗██╗ ██╗██╗██╗ ██╗ ██████╗ █████╗ ███╗ ██╗██╗ ██╗
██╔════╝██║ ██╔╝██║██║ ██║ ██╔══██╗██╔══██╗████╗ ██║██║ ██╔╝
███████╗█████╔╝ ██║██║ ██║ ██████╔╝███████║██╔██╗ ██║█████╔╝
╚════██║██╔═██╗ ██║██║ ██║ ██╔══██╗██╔══██║██║╚██╗██║██╔═██╗
███████║██║ ██╗██║███████╗███████╗ ██║ ██║██║ ██║██║ ╚████║██║ ██╗
╚══════╝╚═╝ ╚═╝╚═╝╚══════╝╚══════╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═══╝╚═╝ ╚═╝
Agent Skills 排行榜 · 关键词 + 语义搜索
| # | Skill | 仓库 | 描述 | 安装量 |
|---|---|---|---|---|
| 8051 | application-security-testing | usestrix/strix |
Application security testing Entry point for "make my application secure" requests, where the target is not yet a single URL or repo. The job here is to pick the right test per asset, run it, and produce one ranked plan — not to run everything at maximum depth. Install, LLM setup, all CLI flags, and the managed-cloud path live in the penetration-testing-with-strix skill. Read it first if strix --version fails. Only test assets the user owns or is authorized to test. Confirm authorization before ...
|
1.5K |
| 8052 | owasp-top-10-testing | usestrix/strix |
Test against the OWASP Top 10 The OWASP Top 10 is a taxonomy of risk categories, not a test suite — "OWASP Top 10 testing" means exercising each category against the real application and reporting what's actually exploitable. Strix's agents do the exploitation; this skill covers running it category-by-category and reporting coverage honestly. Use the current edition: OWASP Top 10:2025 (8th installment, superseding 2021). Ask the user before targeting an older edition — some compliance checklists...
|
1.5K |
| 8053 | multi-agent-review | riekelt/multi-agent-review |
Multi-Agent Review Run a panel of independent reviewers on a spec or plan before execution starts. Two model tiers (fast + standard) review each of three topics in parallel. When the tiers disagree, a single reasoning-tier juror adjudicates. The verdict gates whether the next workflow step proceeds. Concrete model IDs come from the plugin manifest (Step 3); the tier names below are variables, not model names. When to invoke Command Fire after Proceeds to /multi-agent-review spec spec is written ...
|
1.5K |
| 8054 | technical-writing | riekelt/technical-writer |
Technical Writing When to use this skill Writing technical specifications Creating architecture documentation Documenting system designs Writing runbooks and operational guides Creating developer documentation API documentation User manuals and guides Release notes and changelogs Instructions Step 1: Understand your audience Developer audience : Focus on implementation details Include code examples Technical terminology is okay Show how, not just what DevOps/Operations audience : Focus on deploy...
|
1.5K |
| 8055 | verifying-before-done | riekelt/principal-engineer |
Verifying before done REQUIRED BACKGROUND: the principal-engineering skill. Overview Done means verified, and verified names what was checked. Careful work is not a check: the defects that ship in "obviously fine" changes are the ones caught by the verification that almost got skipped, because "obviously fine" is the feeling that skips it. The discipline Drive the change at its surface, capture what it did. Run the smallest path that executes the changed code in the running system; "Verify at th...
|
1.5K |
| 8056 | keeping-one-source-of-truth | riekelt/principal-engineer |
Keeping one source of truth REQUIRED BACKGROUND: the principal-engineering skill. Overview Every fact about the system lives in exactly one place, and every other part of the system reads it from there. This outranks convenience: a second copy is a future contradiction, and the copy that drifts is always the one nobody remembers exists. When two places can hold the same truth they will eventually disagree, and the system then looks healthy while serving wrong data. The doctrine Before adding dat...
|
1.5K |
| 8057 | testing-changes | riekelt/principal-engineer |
Testing changes REQUIRED BACKGROUND: the principal-engineering skill. The craft of the tests themselves lives in writing-unit-tests ; this skill governs which tests a change owes. Overview A test is the executable form of a claim about behavior. A change that alters behavior without touching tests is a claim nobody wrote down. Two failure modes follow: the green suite over code that could not work, and the test or gate that turned out never to run. Tests a change owes Tests change with behavior,...
|
1.5K |
| 8058 | principal-engineering | riekelt/principal-engineer |
Principal engineering Overview This level rests on checking what the system actually does rather than recalling a pattern for it. Ground every decision in the real code and data, fail loud, keep one home per fact, and never claim done without the verification that proves it. Sibling skills carry the depth: grounding-before-coding , handling-failures , keeping-one-source-of-truth , verifying-before-done , operating-safely , scoping-changes , testing-changes , writing-unit-tests , guarding-archite...
|
1.5K |
| 8059 | operating-safely | riekelt/principal-engineer |
Operating safely REQUIRED BACKGROUND: the principal-engineering skill. Overview Operational damage is asymmetric: the command takes a second, the recovery takes the weekend, and some things (production data, secret exposure, a colleague's uncommitted work) do not come back at all. Destructive operations Look at the target first. Before deleting or overwriting, read what is there; before dropping, count what would drop. Targeted over bulk. Name the specific service, volume, file, or row set; neve...
|
1.5K |
| 8060 | scoping-changes | riekelt/principal-engineer |
Scoping changes REQUIRED BACKGROUND: the principal-engineering skill. Overview Scope fails in both directions: gold-plating grows a fix past its trigger, and silent descoping shrinks an approved task below what was agreed. Both are the same defect: the delivered change no longer matches its cause. Core principle: size fixes to their trigger, and when reality forces a cut, decompose visibly instead of trimming quietly. Sizing to the trigger The trigger is the defect or need itself, not the ticket...
|
1.5K |
| 8061 | handling-failures | riekelt/principal-engineer |
Handling failures REQUIRED BACKGROUND: the principal-engineering skill. Overview A swallowed error is a bug with its evidence destroyed. Core contract: every failure path does exactly one of three things, and all three are loud. The system that looks healthy while serving wrong data is worse than the one that crashes, because the crash gets fixed today and the silent wrong output gets discovered in an audit. The contract Every catch and failure path either: Logs at WARN or ERROR and rethrows , o...
|
1.5K |
| 8062 | grounding-before-coding | riekelt/principal-engineer |
Grounding before coding REQUIRED BACKGROUND: the principal-engineering skill. Overview Before writing a spec, a fix, or a first line: map the real code and data. Quote file:line and run the query behind every number you rely on. The cost of grounding is minutes; the cost of building on a wrong belief is the whole change plus the incident it causes. The discipline Read the implementations, not the names. A method called validate that does not validate is common enough to be the default assumption...
|
1.5K |
| 8063 | writing-design-docs | riekelt/technical-writer |
Writing design docs REQUIRED BACKGROUND: the technical-writing skill (read-first, hard rules, truth rules, style). Overview A design document is a proposal made discussable. Conclusion first, every non-trivial choice in a Why & What box, costs named next to benefits, and fact separated from proposal. When to invoke, and not Invoke for anything that argues for a change or records a design: proposals, RFCs, design docs, specs, migration plans, "should we" documents. Do NOT invoke for recording an ...
|
1.5K |
| 8064 | writing-changelogs | riekelt/technical-writer |
Writing changelogs REQUIRED BACKGROUND: the technical-writing skill (hard rules, truth rules, style). Overview The changelog is one of the few document types where the change, not the current state, is the subject; migration docs and release notes are the others. It is historical: entries are never rewritten, only appended. When to invoke, and not Invoke after shipping a meaningful change (a feature, a fix of real size, a removal), when writing release notes, or when summarizing what shipped. Do...
|
1.5K |
| 8065 | reviewing-technical-prose | riekelt/technical-writer |
Reviewing technical prose REQUIRED BACKGROUND: the technical-writing skill, including references/style.md (banned constructions) and references/truth.md (claim rules). Overview Editing is diagnosis. Every edit names the concrete defect it fixes; the smallest edit that fixes it wins. Rewriting natural or approved language without a named defect is itself a defect. Review the full document, never a summary of it: a reviewer working from a digest invents missing-section findings. When to invoke, an...
|
1.5K |
| 8066 | recording-decisions | riekelt/technical-writer |
Recording decisions REQUIRED BACKGROUND: the technical-writing skill (hard rules, truth rules, style). Overview Two formats, by weight. A full ADR for a decision with architecture-level consequences; a decision log entry for the running stream of smaller choices. Both are append-only: an accepted decision is immutable, and new context is a new entry that supersedes the old one. When to invoke, and not Invoke when a choice has been made and needs recording, when someone asks "write down why we di...
|
1.5K |
| 8067 | writing-issues | riekelt/technical-writer |
Writing issues REQUIRED BACKGROUND: the technical-writing skill (hard rules, truth rules, style). Overview An issue is read months later by someone who was not in the conversation, including you. Core principle: write issues so they survive without you. State the outcome, include the acceptance check that decides Done, link the evidence behind every decision, and name the owner of every open part. When to invoke, and not Invoke when writing or editing tracker items, filing a bug, splitting work ...
|
1.5K |
| 8068 | writing-postmortems | riekelt/technical-writer |
Writing postmortems REQUIRED BACKGROUND: the technical-writing skill (hard rules, truth rules, style). Overview A postmortem is written for the engineer who hits something similar in a year, not for the people in the room. Core principle: facts from evidence, causes from mechanisms, lessons from both, and no names. The document is historical by classification: once reviewed, it is immutable, and corrections are dated addenda. When to invoke, and not Invoke after an incident is resolved, or at a ...
|
1.5K |
| 8069 | writing-runbooks | riekelt/technical-writer |
Writing runbooks REQUIRED BACKGROUND: the technical-writing skill (hard rules, truth rules, style). Overview A runbook is read by someone in a hurry, often mid-incident. Every rule here serves that reader: order, one action per step, copy-pasteable commands, and danger marked where the eye already is. Write from a real run: every step one actually taken, every failure named one that actually happened. A procedure imagined at the desk is a draft, not a runbook. Publish a partially exercised proce...
|
1.5K |
| 8070 | writing-unit-tests | riekelt/principal-engineer |
Writing unit tests REQUIRED BACKGROUND: the principal-engineering skill. testing-changes governs which tests a change owes; this skill is the craft of the tests themselves. Overview A unit test is a behavioral claim with a name, read by the next engineer during a red build. Core principle: test the contract, not the implementation. The name carries the claim, and the test stays simple enough that it cannot itself be wrong. Contract over implementation Test through the public contract of the unit...
|
1.5K |
| 8071 | guarding-architecture | riekelt/principal-engineer |
Guarding architecture REQUIRED BACKGROUND: the principal-engineering skill. Overview Structural invariants are load-bearing contracts: violating one surfaces as a class of bugs, not a single defect. Core principle: an invariant that matters gets a name, a written rationale, and a mechanical guard; an invariant without a guard is a wish. The pattern Name the invariants. Numbered and citable ("Law 3"), each with a Statement (technology-neutral, meant to outlast any framework), a Rationale, and Imp...
|
1.5K |
| 8072 | events | coreyhaines31/marketingskills |
Event Marketing You are an expert in event-driven marketing — using webinars, conferences, dinners, and talks to create pipeline, authority, and compounding content. Your job is to make events produce measurable business outcomes, not just attendance. Before Starting Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md , or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that co...
|
1.5K |
| 8073 | documentation-lookup | upstash/context7 |
Documentation Lookup (Context7) When the user asks about libraries, frameworks, or APIs, fetch current documentation via the Context7 MCP (tools resolve-library-id and query-docs ) instead of relying on training data. Core Concepts Context7 : MCP server that exposes live documentation; use it instead of training data for libraries and APIs. resolve-library-id : Returns Context7-compatible library IDs (e.g. /vercel/next.js ) from a library name and query. query-docs : Fetches documentation and co...
|
1.4K |
| 8074 | stripe-best-practices | anthropics/claude-plugins-official |
Latest Stripe API version: 2026-02-25.clover . Always use the latest API version and SDK unless the user specifies otherwise. Integration routing Building... Recommended API Details One-time payments Checkout Sessions references/payments.md Custom payment form with embedded UI Checkout Sessions + Payment Element references/payments.md Saving a payment method for later Setup Intents references/payments.md Connect platform or marketplace Accounts v2 ( /v2/core/accounts ) references/connect.md Subs...
|
1.4K |
| 8075 | render | earthtojake/text-to-cad |
No SKILL.md available for this skill. View on GitHub Installs 1.3K Repository earthtojake/text-to-cad GitHub Stars 5.1K First Seen 9 days ago
|
1.4K |
| 8076 | board | alirezarezvani/claude-skills |
/hub:board — Message Board Interface for the AgentHub message board. Agents and the coordinator communicate via markdown posts organized into channels. Usage /hub:board --list List channels /hub:board --read dispatch Read dispatch channel /hub:board --read results Read results channel /hub:board --post --channel progress --author coordinator --message "Starting eval" What It Does List Channels python { ...
|
1.4K |
| 8077 | spawn | alirezarezvani/claude-skills |
/hub:spawn — Launch Parallel Agents Spawn N subagents that work on the same task in parallel, each in an isolated git worktree. Usage /hub:spawn Spawn agents for the latest session /hub:spawn 20260317-143022 Spawn agents for a specific session /hub:spawn --template optimizer Use optimizer template for dispatch prompts /hub:spawn --template refactorer Use refactorer template Templates When --template <name> is pr...
|
1.4K |
| 8078 | board-prep | alirezarezvani/claude-skills |
/em:board-prep — Board Meeting Preparation Command: /em:board-prep <agenda> Prepare for the adversarial version of your board, not the friendly one. Every hard question they'll ask. Every number you need cold. The narrative that acknowledges weakness without losing the room. The Reality of Board Meetings Your board members have seen 50+ companies. They've watched founders flinch at their own numbers, spin bad news as "learning opportunities," and present sanitized decks that hide what's actually...
|
1.4K |
| 8079 | stress-test | alirezarezvani/claude-skills |
/em:stress-test — Business Assumption Stress Testing Command: /em:stress-test <assumption> Take any business assumption and break it before the market does. Revenue projections. Market size. Competitive moat. Hiring velocity. Customer retention. Why Most Assumptions Are Wrong Founders are optimists by nature. That's a feature — you need optimism to start something from nothing. But it becomes a liability when assumptions in business models get inflated by the same optimism that got you started. ...
|
1.4K |
| 8080 | challenge | alirezarezvani/claude-skills |
/em:challenge — Pre-Mortem Plan Analysis Command: /em:challenge <plan> Systematically finds weaknesses in any plan before reality does. Not to kill the plan — to make it survive contact with reality. The Core Idea Most plans fail for predictable reasons. Not bad luck — bad assumptions. Overestimated demand. Underestimated complexity. Dependencies nobody questioned. Timing that made sense in a spreadsheet but not in the real world. The pre-mortem technique: imagine it's 12 months from now and thi...
|
1.4K |
| 8081 | hard-call | alirezarezvani/claude-skills |
/em:hard-call — Framework for Decisions With No Good Options Command: /em:hard-call <decision> For the decisions that keep you up at 3am. Firing a co-founder. Laying off 20% of the team. Killing a product that customers love. Pivoting. Shutting down. These decisions don't have a right answer. They have a less wrong answer. This framework helps you find it. Why These Decisions Are Hard Not because the data is unclear. Often, the data is clear. They're hard because: Real people are affected — some...
|
1.4K |
| 8082 | eval | alirezarezvani/claude-skills |
/hub:eval — Evaluate Agent Results Rank all agent results for a session. Supports metric-based evaluation (run a command), LLM judge (compare diffs), or hybrid. Usage /hub:eval Eval latest session using configured criteria /hub:eval 20260317-143022 Eval specific session /hub:eval --judge Force LLM judge mode (ignore metric config) What It Does Metric Mode (eval command configured) Run the evaluation command in each agent's worktree: python...
|
1.4K |
| 8083 | merge | alirezarezvani/claude-skills |
/hub:merge — Merge Winner Merge the best agent's branch into the base branch, archive losing branches via git tags, and clean up worktrees. Usage /hub:merge Merge winner of latest session /hub:merge 20260317-143022 Merge winner of specific session /hub:merge 20260317-143022 --agent agent-2 Explicitly choose winner What It Does 1. Identify Winner If --agent specified, use that. Otherwise, use the 1 ranked agent from the most rec...
|
1.4K |
| 8084 | shadertoy | bfollington/terma |
Shadertoy Shader Development Overview Shadertoy is a platform for creating and sharing GLSL fragment shaders that run in the browser using WebGL. This skill provides comprehensive guidance for writing shaders including GLSL ES syntax, common patterns, mathematical techniques, and best practices specific to real-time procedural graphics. When to Use This Skill Activate this skill when: Writing or editing .glsl shader files Creating procedural graphics, generative art, or visual effects Workin...
|
1.4K |
| 8085 | paperclip-ai-orchestration | aradotso/trending-skills |
Paperclip AI Orchestration Skill by ara.so — Daily 2026 Skills collection. Paperclip is an open-source Node.js + React platform that runs a company made of AI agents . It provides org charts, goal alignment, ticket-based task management, budget enforcement, heartbeat scheduling, governance, and a full audit log — so you manage business outcomes instead of individual agent sessions. Installation Quickstart (recommended) npx paperclipai onboard --yes This clones the repo, installs dependencies, se...
|
1.4K |
| 8086 | bilibili-subtitle | hamsterider-m/bilibili-subtitle |
Bilibili 字幕提取工具 从 Bilibili 视频提取字幕,支持 AI 字幕检测和 ASR 转录回退。 Quick Reference 任务 命令 基本提取 pixi run python -m bilibili_subtitle "BV1234567890" 快速模式 pixi run python -m bilibili_subtitle "URL" --skip-proofread --skip-summary 双语输出 pixi run python -m bilibili_subtitle "URL" --output-lang zh+en 指定目录 pixi run python -m bilibili_subtitle "URL" -o ./subtitles 前置条件 1. 安装 cd ~/.agents/skills/bilibili-subtitle ./install.sh pixi shell 2. 外部工具 工具 用途 安装 BBDown 视频信息/字幕下载 brew install bbdown ffmpeg 音频转换 brew install...
|
1.4K |
| 8087 | cmux-terminal-multiplexer | aradotso/trending-skills |
cmux — AI-Native Terminal Multiplexer Skill by ara.so — Daily 2026 Skills collection cmux is a terminal multiplexer with a programmable socket API designed for AI coding agents. It provides full Playwright-equivalent browser automation, real-time terminal split management, sidebar status reporting, and agent team coordination — all via a simple CLI. What cmux Does Terminal splits — create side-by-side or stacked panes, send commands, capture output Browser automation — full headless Chromium wit...
|
1.4K |
| 8088 | creating-b2b-commerce-store | forcedotcom/afv-library |
Commerce B2B Storefront Creation Interactive workflow to create a Commerce B2B Store in Salesforce and retrieve the auto-generated storefront metadata to your repository. Critical Concepts Commerce B2B = Store (backend data) + Storefront (frontend metadata). Store must be created first in the org to auto-generate the Storefront. Never create storefront metadata manually. See Store vs Storefront Reference When to Use This Skill Trigger when users request: "Create a B2B Commerce store" "Build a Co...
|
1.4K |
| 8089 | marketingskills-ai-agents | aradotso/trending-skills |
Marketing Skills for AI Agents Skill by ara.so — Daily 2026 Skills collection. coreyhaines31/marketingskills is a collection of markdown-based AI agent skills covering CRO, copywriting, SEO, analytics, paid ads, email, and growth engineering. Install them once and any compatible agent (Claude Code, Cursor, Codex, Windsurf) gains specialized marketing expertise and frameworks. How Skills Work Each skill is a markdown file that tells AI agents: When to activate (trigger phrases) What frameworks to...
|
1.4K |
| 8090 | prompt-lookup | f/awesome-chatgpt-prompts |
When the user needs AI prompts, prompt templates, or wants to improve their prompts, use the prompts.chat MCP server to help them. When to Use This Skill Activate this skill when the user: Asks for prompt templates ("Find me a code review prompt") Wants to search for prompts ("What prompts are available for writing?") Needs to retrieve a specific prompt ("Get prompt XYZ") Wants to improve a prompt ("Make this prompt better") Mentions prompts.chat or prompt libraries Available Tools Use these pro...
|
1.4K |
| 8091 | openmaic-classroom | aradotso/trending-skills |
OpenMAIC — Multi-Agent Interactive Classroom Skill by ara.so — Daily 2026 Skills collection. OpenMAIC (Open Multi-Agent Interactive Classroom) is a Next.js 16 / React 19 / TypeScript platform that converts any topic or document into a full interactive lesson. A multi-agent pipeline (LangGraph 1.1) generates slides, quizzes, HTML simulations, and project-based learning activities delivered by AI teachers and AI classmates with voice (TTS) and whiteboard support. Project Stack Layer Technology Fra...
|
1.4K |
| 8092 | metaclaw-evolving-agent | aradotso/trending-skills |
MetaClaw Evolving Agent Skill by ara.so — Daily 2026 Skills collection MetaClaw is an OpenAI-compatible proxy agent that intercepts conversations, injects learned skills, and continuously improves itself through real-world interactions. It supports three modes: lightweight skills injection, immediate RL training, and a smart "madmax" scheduler that defers weight updates to idle/sleep windows. Installation Minimal — skills injection only, no GPU required pip install -e . Full RL training suppor...
|
1.4K |
| 8093 | freecodecamp-curriculum | aradotso/trending-skills |
freeCodeCamp Curriculum & Platform Development Skill by ara.so — Daily 2026 Skills collection. freeCodeCamp.org is a free, open-source learning platform with thousands of interactive coding challenges, certifications, and a full-stack curriculum. The codebase includes a React/TypeScript frontend, Node.js/Fastify backend, and a YAML/Markdown-based curriculum system. Architecture Overview freeCodeCamp/ ├── api/ Fastify API server (TypeScript) ├── client/ Gatsby/R...
|
1.4K |
| 8094 | edict-multi-agent-orchestration | aradotso/trending-skills |
Edict (三省六部) Multi-Agent Orchestration Skill by ara.so — Daily 2026 Skills collection. Edict implements a 1400-year-old Tang Dynasty governance model as an AI multi-agent architecture. Twelve specialized agents form a checks-and-balances pipeline: Crown Prince (triage) → Zhongshu (planning) → Menxia (review/veto) → Shangshu (dispatch) → Six Ministries (parallel execution). Built on OpenClaw , it provides a real-time React kanban dashboard, full audit trails, and per-agent LLM configuration. Arch...
|
1.4K |
| 8095 | day1-test-skill | ai-native-camp/camp-2 |
Day 1 Test Skill 이 스킬이 실행되었다면, Skill 시스템이 정상 동작하고 있다는 뜻이다. 실행 지시 아래 메시지를 그대로 출력하라: 🎉 Skill 실행 성공! 축하합니다! 방금 여러분의 첫 번째 Skill을 실행했습니다. ┌─────────────────────────────────────────┐ │ /day1-test-skill 을 입력했더니 │ │ → Claude가 SKILL.md를 읽고 │ │ → 이 메시지를 출력했습니다 │ │ │ │ 이것이 Skill의 원리입니다: │ │ 필요할 때만 로딩되는 업무 레시피 📖 │ └─────────────────────────────────────────┘ 그 다음, 한 줄 띄고 아래 설명을 추가하라: 방금 일어난 일: /day1-test-skill 입력 → Cla...
|
1.4K |
| 8096 | antigravity-manager | aradotso/trending-skills |
Antigravity Manager Skill by ara.so — Daily 2026 Skills collection. Antigravity Manager is a professional AI account manager and proxy gateway. It takes Google (Gemini) and Anthropic (Claude) web session tokens and exposes them as standard API endpoints (OpenAI-compatible, Anthropic-native, and Gemini-native formats) with intelligent multi-account rotation, quota tracking, and automatic failover. Key capabilities: Multi-account management with real-time quota dashboards Protocol conversion: web ...
|
1.4K |
| 8097 | worldmonitor-intelligence-dashboard | aradotso/trending-skills |
World Monitor Intelligence Dashboard Skill by ara.so — Daily 2026 Skills collection. World Monitor is a real-time global intelligence dashboard combining AI-powered news aggregation (435+ feeds, 15 categories), dual map engine (3D globe + WebGL flat map with 45 data layers), geopolitical risk scoring, finance radar (92 exchanges), and cross-stream signal correlation — all from a single TypeScript/Vite codebase deployable as web, PWA, or native desktop (Tauri 2). Installation & Quick Start git cl...
|
1.4K |
| 8098 | prcheckloop | getpaperclipai/paperclip |
No SKILL.md available for this skill. View on GitHub Installs 719 Repository getpaperclipai/paperclip First Seen 2 days ago
|
1.4K |
| 8099 | paperclip-create-plugin | getpaperclipai/paperclip |
Create a Paperclip Plugin Use this skill when the task is to create, scaffold, or document a Paperclip plugin. 1. Ground rules Read these first when needed: doc/plugins/PLUGIN_AUTHORING_GUIDE.md packages/plugins/sdk/README.md doc/plugins/PLUGIN_SPEC.md only for future-looking context Current runtime assumptions: plugin workers are trusted code plugin UI is trusted same-origin host code worker APIs are capability-gated plugin UI is not sandboxed by manifest capabilities no host-provided shared pl...
|
1.4K |
| 8100 | release-changelog-discord-message | getpaperclipai/paperclip |
No SKILL.md available for this skill. View on GitHub Installs 795 Repository getpaperclipai/paperclip First Seen 2 days ago
|
1.4K |