「search」の検索結果

Read and manage Asana tasks, projects, sections, comments, and workspaces. Use this whenever the user wants to list or search tasks, create or update a task, complete a task, comment on a task, move tasks between projects or sections, look up a project or workspace, or ask "what's on my Asana list" — even if they don't say "API". Also use it for any app.asana.com URL or an Asana task/project gid. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.

日本語の概要は準備中です。原文の説明を表示しています。

Search, read, create, update, export, and share files in Google Drive. Use this whenever the user wants to find a file in Drive, read a Google Doc or Sheet, upload a file, move something into a folder, change sharing permissions, or asks "what's in my Drive" — even if they don't say "API". Also use it for any URL under drive.google.com or docs.google.com, or a mention of a Drive file ID. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.

日本語の概要は準備中です。原文の説明を表示しています。

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 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.

日本語の概要は準備中です。原文の説明を表示しています。

Work with a Grafana instance — search and read dashboards, run datasource queries (Prometheus, Loki, PostgreSQL, etc.), inspect alert rules and silences, post annotations, and manage folders. Use this whenever the user mentions a Grafana dashboard, panel, or alert; pastes a Grafana URL; asks "what does this dashboard show", "query this metric in Grafana", "is this alert firing", "silence this alert", or wants to create/export a dashboard — 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 Datadog monitoring data — logs, metrics, monitors, dashboards, events, SLOs, traces, and incidents. Use this whenever the user wants to search logs, look at a metric, check which monitors are alerting, investigate a trace, pull SLO status, mute an alert, or ask "what's happening in Datadog" — even if they don't say "API". Also use it for any URL under *.datadoghq.com. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.

日本語の概要は準備中です。原文の説明を表示しています。

Search Haskell APIs using Hoogle. Use when working with Haskell projects to look up function signatures, find functions by type, discover library documentation, or identify which module exports an item.

日本語の概要は準備中です。原文の説明を表示しています。

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

日本語の概要は準備中です。原文の説明を表示しています。

Automate and research the GitHub Copilot app desktop experience. Use for driving Copilot App sessions, creating isolated app experiments, mapping app UI/accessibility controls, taking app screenshots, saving PNG captures, optimizing WebP images, testing prompts without submitting, using app/session APIs, canvases, automations, macOS Accessibility, AppleScript, and safe end-to-end Copilot App workflow probes.

日本語の概要は準備中です。原文の説明を表示しています。

Find unclaimed open source issues that match the user's skills and experience level. Searches for issues created by maintainers/org admins, checks contribution eligibility, and ranks by learning value. Use when looking for an issue to contribute to, starting OSS contributions, or finding GSoC-friendly issues. Not for finding problems that nobody has filed an issue for yet. Use oss-find-real-issues for that.

日本語の概要は準備中です。原文の説明を表示しています。

Handle PR review feedback - understand reviewer comments, research their concerns, and help the user address them. The LLM explains what reviewers want and why; the user decides how to respond and writes the code. Use when you receive review comments on a submitted PR. Not for opening the PR in the first place, which is oss-submit-pr. If the feedback is a failing CI job, use oss-debug-ci.

日本語の概要は準備中です。原文の説明を表示しています。

Research an issue deeply and present all context to the user. but the user writes the code. The LLM investigates code paths, finds relevant files, explains patterns, and identifies constraints. The user thinks through the approach and implements it. Use when ready to start working on an issue after oss-prep-to-contribute. Not for writing tests or documentation as a standalone contribution. Use oss-write-tests or oss-write-docs for those.

日本語の概要は準備中です。原文の説明を表示しています。

Transform any research material into SEO+GEO-optimized blog posts for Knox Hub. Takes any input (URL, article text, notes, video transcript, competitor post, topic idea) and rewrites it as natural human-sounding content, then fills in all fields for the Knox Hub post editor: title, excerpt, SEO settings, FAQ schema, table of contents, sticky sidebar, and full article content in Markdown. Output is ready to copy-paste into your blog/CMS post editor. Use when asked to "write a post", "rewrite this", "сделай пост", "напиши статью", "перепиши это для блога", "create blog post", or any content creation task.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you want to benchmark and improve an existing repo skill through repeated evals, prompt mutations, and score tracking.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you want a research analysis of how a company, creator, or newsletter markets itself across channels, voice, and tactics.

日本語の概要は準備中です。原文の説明を表示しています。

Use when searching for buying signals, detecting intent data, scoring prospect readiness, or monitoring accounts for trigger events. Triggers: 'scan for signals', 'find buying signals', 'who is ready to buy', 'intent signals', 'signal scoring', 'account signals'.

日本語の概要は準備中です。原文の説明を表示しています。

当用户要写出高质量 Goal Prompt，把模糊、战略性、多步骤、证据不足、持续/自动化或容易跑偏的请求整理成可执行、可验证、可暂停的目标契约时使用。适用于写 goal、优化任务提示词、明确 done/success criteria、deep research 后定战略、大改前 inventory、修复跑偏计划、识别可委托的重复 workflow、为 Codex 或 Claude Code 准备执行任务；默认一次性交付只生成 Goal Prompt，只有存在真实后续迭代需求时才追加 Loop Prompt，不执行 goal 或 loop，也不创建自动化。

日本語の概要は準備中です。原文の説明を表示しています。

Search your conversation history using ripgrep. Use when you need to find previous messages, file edits, tool calls, or decisions from earlier in the session.

日本語の概要は準備中です。原文の説明を表示しています。

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.

日本語の概要は準備中です。原文の説明を表示しています。

Search Google Cloud (GKE) server logs of the PROD environment. Use when troubleshooting a production incident that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check PROD logs", "check production server logs", or gives a production timeline from a client console log.

日本語の概要は準備中です。原文の説明を表示しています。

Stream and search iOS device logs. Use proactively when debugging iOS issues or when user asks to check device logs.

日本語の概要は準備中です。原文の説明を表示しています。

Search Google Cloud (GKE) server logs of the DEV environment (dev.voxt.ai). Use when troubleshooting anything that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check GCP logs", "check server logs on dev", or gives a dev.voxt.ai timeline from a client console log.

日本語の概要は準備中です。原文の説明を表示しています。

Create user-centered, accessible interface copy (microcopy) for digital products including buttons, labels, error messages, notifications, forms, onboarding, empty states, success messages, and help text. Use when writing or editing any text that appears in apps, websites, or software interfaces, designing conversational flows, establishing voice and tone guidelines, auditing product content for consistency and usability, reviewing UI strings, or improving existing interface copy. Applies UX writing best practices based on four quality standards — purposeful, concise, conversational, and clear. Includes accessibility guidelines, research-backed benchmarks (sentence length, comprehension rates, reading levels), expanded error patterns, tone adaptation frameworks, and comprehensive reference materials.

日本語の概要は準備中です。原文の説明を表示しています。

LLM brand manipulation — build a consensus web so ChatGPT, Claude, Perplexity, and Google AI Overviews mention your brand when people ask about your category. Uses surround sound methodology, entity SEO, and LLM citation science. Use when "get mentioned in AI", "LLM brand presence", "surround sound", "AI search visibility", "Perplexity ranking", "ChatGPT mentions", "AI Overview inclusion", "entity authority", "brand mentions in AI", or any request to influence how AI systems perceive and recommend your brand.

日本語の概要は準備中です。原文の説明を表示しています。