跳至主要內容
kitlocal.dev

代理技能

教導程式開發代理完成可重複任務的技能,並附上其來源與包含的內容。

4 項資源

搜尋在 KitLocal 的目錄中執行。你在此輸入的內容不會傳送給 GitHub 或任何其他服務。

4 筆結果

  • A guide for building high-quality MCP servers, in Python (FastMCP) or Node/TypeScript, so an LLM can use an external API through well-designed tools.

    精選 + 即時Anthropic · Complete terms in LICENSE.txt更新於 19 天前

    mcpserverauthoring
  • Guidance for making intentional visual design choices (direction, typography, polish) when building new UI or reshaping an existing one, so results do not look like templated defaults.

    精選 + 即時Anthropic · Complete terms in LICENSE.txt更新於 2 個月前

    designuifrontend
  • Guides an agent through creating, editing and evaluating Agent Skills, including benchmarking a skill and tuning its description so it triggers reliably.

    精選 + 即時Anthropic更新於 7 個月前

    agent-skillsauthoringevals
  • A toolkit for testing local web applications with Playwright: verify frontend behavior, debug UI problems, capture screenshots and read browser logs.

    精選 + 即時Anthropic · Complete terms in LICENSE.txt更新於 7 個月前

    playwrighttestingbrowser

KitLocal · GitHub

探索個別技能

從已設定的 GitHub 儲存庫索引的 SKILL.md 檔案。星數與更新時間屬於儲存庫,而非個別技能。

星數屬於 GitHub 儲存庫,因此同一儲存庫中的技能共用同一個數字。

快照:2026年11月15日 清晨5:54 · 內建

68 個技能,來自 3 個儲存庫

  1. 01
    vercel-composition-patterns ↗

    vercel-labs/agent-skills · skills/composition-patterns/SKILL.md · 觀測於 2026年11月15日

    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.

    npx skills add vercel-labs/agent-skills
    另有 8 個來自 vercel-labs/agent-skills
    • deploy-to-vercel ↗

      Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

    • vercel-react-best-practices ↗

      React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

    • vercel-react-native-skills ↗

      React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

    • vercel-react-view-transitions ↗

      Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.

    • vercel-cli-with-tokens ↗

      Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".

    • vercel-optimize ↗

      Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.

    • web-design-guidelines ↗

      Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    • writing-guidelines ↗

      Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".

    ★ 3.4萬

  2. 02
    brainstorming ↗

    obra/superpowers · skills/brainstorming/SKILL.md · 觀測於 2026年11月15日

    You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

    npx skills add obra/superpowers
    另有 14 個來自 obra/superpowers
    • diagnosing-superpowers ↗

      Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    • dispatching-parallel-agents ↗

      Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

    • executing-plans ↗

      Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

    • finishing-a-development-branch ↗

      Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

    • receiving-code-review ↗

      Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    • requesting-code-review ↗

      Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    • subagent-driven-development ↗

      Use when executing implementation plans with independent tasks in the current session

    • systematic-debugging ↗

      Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    • test-driven-development ↗

      Use when implementing any feature or bugfix, before writing implementation code

    • using-git-worktrees ↗

      Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

    • using-superpowers ↗

      Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

    • verification-before-completion ↗

      Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

    • writing-plans ↗

      Use when you have a spec or requirements for a multi-step task, before touching code

    • writing-skills ↗

      Use when creating new skills, editing existing skills, or verifying skills work before deployment

    ★ 32萬

  3. 03
    aspnet-core ↗

    openai/skills · skills/.curated/aspnet-core/SKILL.md · 觀測於 2026年11月15日

    Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades.

    npx skills add openai/skills
    另有 43 個來自 openai/skills
    • chatgpt-apps ↗

      Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, register UI resources, wire the MCP Apps bridge or ChatGPT compatibility APIs, apply Apps SDK metadata or CSP or domain settings, or produce a docs-aligned project scaffold. Prefer a docs-first workflow by invoking the openai-docs skill or OpenAI developer docs MCP tools before generating code.

    • cli-creator ↗

      Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read/write commands, return stable JSON, manage auth, and pair with a companion skill.

    • cloudflare-deploy ↗

      Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.

    • define-goal ↗

      Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.

    • figma-code-connect-components ↗

      Connects Figma design components to code components using Code Connect mapping tools. Use when user says "code connect", "connect this component to code", "map this component", "link component to code", "create code connect mapping", or wants to establish mappings between Figma designs and code implementations. For canvas writes via `use_figma`, use `figma-use`.

    • figma-create-design-system-rules ↗

      Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.

    • figma-create-new-file ↗

      Create a new blank Figma file. Use when the user wants to create a new Figma design or FigJam file, or when you need a new file before calling use_figma. Handles plan resolution via whoami if needed. Usage — /figma-create-new-file [editorType] [fileName] (e.g. /figma-create-new-file figjam My Whiteboard)

    • figma-generate-design ↗

      Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code'. This is the preferred workflow skill whenever the user wants to build or update a full page, screen, or view in Figma from code or a description. Discovers design system components, variables, and styles via search_design_system, imports them, and assembles screens incrementally section-by-section using design system tokens instead of hardcoded values.

    • figma-generate-library ↗

      Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. This skill teaches WHAT to build and in WHAT ORDER — it complements the `figma-use` skill which teaches HOW to call the Plugin API. Both skills should be loaded together.

    • figma-implement-design ↗

      Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.

    • figma-use ↗

      **MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.

    • figma ↗

      Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.

    • gh-address-comments ↗

      Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.

    • gh-fix-ci ↗

      Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

    • hatch-pet ↗

      Create, repair, validate, visually QA, and package Codex-compatible animated pets and pet spritesheets from character art, generated images, company or prospect brand cues, or visual references. Use when a user wants a lightweight-worker Codex pet workflow, a non-pixel custom pet style, a prospect or company mascot pet, or a full 8x9 animated pet atlas with transparent unused cells, QA contact sheets, and pet.json packaging. This skill composes the installed $imagegen system skill for visual generation and uses bundled scripts for deterministic spritesheet assembly.

    • jupyter-notebook ↗

      Use when the user asks to create, scaffold, or edit Jupyter notebooks (`.ipynb`) for experiments, explorations, or tutorials; prefer the bundled templates and run the helper script `new_notebook.py` to generate a clean starting notebook.

    • linear ↗

      Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.

    • migrate-to-codex ↗

      Migrate supported instruction files, skills, agents, and MCP config into Codex project and global files.

    • netlify-deploy ↗

      Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.

    • notion-knowledge-capture ↗

      Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.

    • notion-meeting-intelligence ↗

      Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

    • notion-research-documentation ↗

      Research across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.

    • notion-spec-to-implementation ↗

      Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.

    • openai-docs ↗

      Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.

    • pdf ↗

      Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.

    • playwright-interactive ↗

      Persistent browser and Electron interaction through `js_repl` for fast iterative UI debugging.

    • playwright ↗

      Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

    • render-deploy ↗

      Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.

    • screenshot ↗

      Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.

    • security-best-practices ↗

      Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.

    • security-ownership-map ↗

      Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions.

    • security-threat-model ↗

      Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.

    • sentry ↗

      Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry CLI; perform read-only queries using the `sentry` command.

    • speech ↗

      Use when the user asks for text-to-speech narration or voiceover, accessibility reads, audio prompts, or batch speech generation via the OpenAI Audio API; run the bundled CLI (`scripts/text_to_speech.py`) with built-in voices and require `OPENAI_API_KEY` for live calls. Custom voice creation is out of scope.

    • transcribe ↗

      Transcribe audio files to text with optional diarization and known-speaker hints. Use when a user asks to transcribe speech from audio/video, extract text from recordings, or label speakers in interviews or meetings.

    • vercel-deploy ↗

      Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

    • winui-app ↗

      Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.

    • yeet ↗

      Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

    • imagegen ↗

      Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.

    • openai-docs ↗

      Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.

    • plugin-creator ↗

      Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new local plugin, add optional plugin structure, or generate or update repo-root `.agents/plugins/marketplace.json` entries for plugin ordering and availability metadata.

    • skill-creator ↗

      Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.

    • skill-installer ↗

      Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

    ★ 2.9萬

依用途瀏覽熱門技能儲存庫

即時搜尋 GitHub 上帶有 agent-skills 標籤的儲存庫,並依星數排序。將開啟 GitHub Discover。

Agent Skills

為你的 AI 代理探索技能

尋找可重複使用的程式開發、研究與日常工作流程指引。你可以選擇排行榜、依任務瀏覽,或查看下方精選技能。

SKILLS.SH

探索熱門技能

Skills.sh 依安裝活躍度為個別技能排名。

這些連結會開啟 skills.sh 的即時排行榜。

SKILLSMP

依使用情境瀏覽技能

依主題探索規模更大的 SkillsMP 目錄,並開啟來源查看詳細資訊。

SkillsMP 所有分類

安裝前請先檢視技能的說明與所有腳本。排名或收錄並不代表已通過安全性審查。

GitHub · Stars

代理技能熱門儲存庫

帶有 agent-skills 標籤的 GitHub 儲存庫,依儲存庫星數排序。

查看完整排行榜
正在載入 GitHub 排行榜…
關於此目錄

內建快照 · 發布於 2026年11月15日 清晨6:05 · 目錄修訂版 5bc079fe355af2214bc0

正在顯示應用程式內建的快照(尚未設定內容來源)。來源處可能已有更新的內容。