2,051 件 ・ 関連度順
概要と使いどころ
Fetch a Linear ticket's title + description (the source of all warp route parameters) from a ticket ID or URL, using whichever Linear access the agent has — a Linear integration/tool if present, otherwise the Linear GraphQL API with LINEAR_API_KEY — and halt clearly if no access is configured. Referenced by every warp deploy/update skill that reads a ticket.
日本語の概要は準備中です。原文の説明を表示しています。
Start the local HTTP registry server for development. Use when testing infra scripts or commands that need a Abacus work private overrides such as RPC URLS.
日本語の概要は準備中です。原文の説明を表示しています。
Debug why a Hyperlane message is not being processed. Use when given a message ID or explorer URL to investigate delivery failures, gas estimation errors, validator issues, or other processing problems.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks Codex to read or write Odysseus data (todos, email, calendar, memory, documents) or to launch/monitor/stop a Cookbook model-serve task through the scoped Codex Agent API. Requires ODYSSEUS_URL and ODYSSEUS_API_TOKEN.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks Claude Code to read or write Odysseus data (todos, email, calendar, memory, documents) or to launch/monitor/stop a Cookbook model-serve task through the scoped Claude Agent API. Requires ODYSSEUS_URL and ODYSSEUS_API_TOKEN.
日本語の概要は準備中です。原文の説明を表示しています。
Automates the Karpathy LLM Wiki workflow: turns web, GitHub, and YouTube URLs into well-structured, citable, wikilinked pages with automatic linting and sourcing — invoke with /pin-llm-wiki
日本語の概要は準備中です。原文の説明を表示しています。
Download full-resolution images from iCloud, Dropbox, Google Photos share links. Use when extracting images from cloud share URLs, remote debugging with screenshots, or downloading shared photo albums.
日本語の概要は準備中です。原文の説明を表示しています。
Pipeline from a URL or DESIGN.md to tokens, decisions and a UI spec. Use when building UI for an existing brand, auditing a design system or fixing visual inconsistency.
日本語の概要は準備中です。原文の説明を表示しています。
Extracts paper recommendations from social-media posts and online articles (小红书 / Xiaohongshu / RedNote, 微信公众号 / WeChat Official Accounts, Twitter / X threads, Reddit posts, Bilibili videos, blog posts, newsletters, Jina Reader URLs), identifies the underlying academic papers, locates the authoritative original sources (arXiv, conference proceedings, DOI), and triages relevance to the user's research before any library action. Use when the user forwards a social-media link, screenshot, or article that mentions a paper / method / model, asks to "find the original paper" from a blog or thread, shares a 调研贴 / 论文推荐 / paper recommendation post, or wants to evaluate whether a buzz-worthy paper is worth reading before adding it to Zotero.
日本語の概要は準備中です。原文の説明を表示しています。
OpenStack Swift object storage service. Provides S3-compatible distributed object storage with containers, ACLs, ring architecture, eventual consistency, large object support (SLO/DLO), tempURL for unauthenticated access, object versioning, and object expiry. Use for deploying, configuring, operating, and troubleshooting OpenStack object storage.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the primary outcome is creating publishable source-attributed content from URLs or supplied material, including research summaries, articles, briefs, and posts whose factual claims and quotations need reader-visible, verifiable citations.
日本語の概要は準備中です。原文の説明を表示しています。
Route requests to summarize files, URLs, images, inline text, or multiple sources. Select the requested format and preserve evidence, exact counts, uncertainty and source coverage through summarization, synthesis and agent-result relay.
日本語の概要は準備中です。原文の説明を表示しています。
Integrates patterns from external sources (URLs or local files) into local skills, agents, and plugins. Use when comparing external agent definitions against local equivalents, extracting best practices from frameworks like GSD or BMAD-METHOD, enhancing local skills with external workflow patterns, or adding interoperability with external tool ecosystems. Runs a 3-phase workflow — parallel candidate mapping, contextual enhancement, and validation — with source attribution and backlog tracking for deferred enhancements.
日本語の概要は準備中です。原文の説明を表示しています。
Badge design and selection knowledge base for shields.io badges in README files. Use when writing or updating READMEs, choosing badge layouts, selecting badge styles, adding project health indicators, or picking Simple Icons logo slugs. Covers shields.io URL encoding rules, static vs dynamic badge selection, style variants (flat/flat-square/for-the-badge/social/plastic), layout patterns (two-tier/inline/centered), project-type badge sets for Python/JS/Rust/Claude plugins, color reference, non-obvious logo slugs, and common anti-patterns to avoid.
日本語の概要は準備中です。原文の説明を表示しています。
Configure Vapi server URLs and webhooks to receive real-time call events, transcripts, tool calls, and end-of-call reports. Use when setting up webhook endpoints, building tool servers, or integrating Vapi events into your application.
日本語の概要は準備中です。原文の説明を表示しています。
See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio, video), and create real time alerts for events from live streams or desktop capture.
日本語の概要は準備中です。原文の説明を表示しています。
Deploys websites, web apps, APIs, and agents to the internet with a strict pre-deploy audit and a preview → health-check → prod flow. Handles plain HTML/CSS/JS pages and static sites (Astro, Hugo, Jekyll, Eleventy, Vite) as well as Next, Remix, Nuxt, SvelteKit, FastAPI, Flask, Express, MCP servers, Claude Agent SDK scripts, Python workers, and Dockerized projects. Routes to free static hosts — Cloudflare Pages, Netlify, GitHub Pages, Render — or to Vercel, Railway, Docker+SSH VPS, or a cloudflared tunnel, and can also run the project locally. Use when the user says "/all-deploy", "/deploy", "/despliega", "deploy this", "ship this", "push to prod", "get this online", "publish my website", "sube mi página web", "publicar mi página", "hosting gratis", "free hosting", "custom domain", "dominio propio", "run it locally", "corre esto localmente", or otherwise asks to publish a site or project to a URL.
日本語の概要は準備中です。原文の説明を表示しています。
High-precision semantic search and content retrieval via Exa API. Use when: (1) Deep research requiring semantic understanding, (2) Code documentation and examples lookup, (3) Company/professional research, (4) AI-powered comprehensive research tasks, (5) URL content extraction with structured output. Triggers: "research", "find papers", "code examples", "company info", "LinkedIn profiles", "deep analysis". Differentiator: Exa excels at semantic/neural search while grok-search is better for real-time news and general web content.
日本語の概要は準備中です。原文の説明を表示しています。
Researches a company from its website and public sources and writes a company profile: what it sells, who buys it, traction, funding, team, hiring, tech stack, key people, red flags and the gaps you still need to fill, every claim tagged with a source and a confidence level. Use it as the first file in a marketing context folder, or to prep a discovery call or qualify a prospect. Triggers: "company research", "company background", "company context for", "qualify this prospect", "discovery call prep", "account brief", or a company URL handed over for research. Not for competitor analysis (use /competitor-research) or customer profiles (use /icp-research).
日本語の概要は準備中です。原文の説明を表示しています。
Extract visual identity from screenshots (primary) or website URL (fallback) and compile into a DESIGN.md-format brand kit — YAML token frontmatter (colors, typography, rounded, spacing, components) + 8 ordered prose sections. The YAML tokens are machine-authoritative; downstream visual skills consume them directly. Writes to marketing/brand/brand-kit.md. Triggers - "brand kit", "brand identity", "visual identity", "design tokens", "extract brand", "DESIGN.md"
日本語の概要は準備中です。原文の説明を表示しています。
Read and manage Jira Cloud issues, projects, boards, sprints, comments, and transitions. Use this whenever the user wants to search issues with JQL, create or update a ticket, transition an issue (move to In Progress / Done), add a comment, check a sprint or board, look up a project, or ask "what's in my Jira queue" — even if they don't say "API". Also use it for any *.atlassian.net URL, an issue key like "PROJ-123", or a JQL string. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
日本語の概要は準備中です。原文の説明を表示しています。
Query and manage PagerDuty — find out who's on call, list and manage incidents, read escalation policies and schedules, trace who got paged and why, acknowledge/resolve/snooze/escalate incidents, and create or update services. Use this whenever the user mentions PagerDuty, on-call, paging, escalation, an incident ID like `PXXXXXX` or `Q...`, asks "who's on call", "page the on-call", "ack this incident", "why wasn't I paged", or pastes a pagerduty.com URL — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
日本語の概要は準備中です。原文の説明を表示しています。
Query and manage Sentry error-tracking data — list and search issues, drill into events and stack traces, inspect projects and releases, resolve/ignore issues, and pull stats. Use this whenever the user mentions a Sentry issue, crash, error group, or exception; pastes a sentry.io or self-hosted Sentry URL; asks "why is this erroring", "how many times has this happened", "what's the top error in {project}", "resolve this issue", or wants a Sentry-based digest — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
日本語の概要は準備中です。原文の説明を表示しています。