「only」の検索結果

Post a sitrep (situation report) for a live incident, in its incident channel: a short fixed-layout update for people who haven't read the whole channel — the current picture and what moved since the previous update. Use on "sitrep", "status update", "where are we", "what's the latest", "catch me up", "summarize the incident so far", when asked to keep posting on a schedule ("post a sitrep every hour until resolved"), or when the oncall memory sets an update cadence for this severity and the incident owner asks Claude to keep it. Reads the channel, alert thread and findings posted, re-reads the one key signal, and writes: status line, TL;DR, impact, what changed since the last sitrep, what's in progress and who has it, what's needed, when the next update comes, one chart. Facts come only from what people said or Claude read first-hand; cause and recovery time are never guessed. Fits one phone screen. Not investigation (`incident-investigate`) or the write-up afterwards (`incident-postmortem`).

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

Write the postmortem for an incident, in its incident channel, once it is mitigated or resolved. Use on "write up this incident", "postmortem", "incident summary", "what happened here for people who weren't around", "draft the retro", or when the oncall memory says incidents of this severity get one. Reads the incident channel (and the alert thread it came from), the investigation findings and the data behind them, and writes a one-screen, zero-context write-up: what happened, impact with numbers, detection, timeline with durations, why it happened, what fixed it, follow-ups with proposed owners, and one before/during/after chart. Posted and pinned in the incident channel as its final pinned post, with edit requests updating that one pinned post in place — unless the person or the team's conventions say write-ups live elsewhere, in which case it is written there and only a link is posted, nothing pinned. A person edits and publishes it; never assigns blame.

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

Read Haskell package documentation, Haddock HTML, Hackage pages, or dependency source for cabal nix-style projects. Prefer locally built/cached docs and source from the cabal store, dist-newstyle, plan.json, and repo-cache; fall back to Hackage only for packages outside the project dependency set or when local docs are unavailable.

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

Use only for reviewing completed Biome PRs, branches, commit ranges, diffs, or working trees against business logic and requirements. Excludes broad code-quality and process audits, triage, reproduction, and implementation.

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

Write unit and E2E tests for Grafana visualization panels and viz utilities to the conventions this repo expects. Use when adding, backfilling, or reviewing tests for panels (barchart, timeseries, table, xychart, heatmap, canvas, etc.), grafana-ui viz components (Table, uPlot, VizLegend, VizTooltip), or grafana-data viz utils; when a panel test only asserts "it rendered" or "it's defined"; when reviewing AI-generated panel tests for slop; or when a canvas/rendering test is flaky.

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

Use before opening a PR, or whenever asked to self-review a diffusers contribution. Applies the same rubric as the `@claude` CI (checks the diff against references/review-rules.md, traces call paths for dead code). Reports findings grouped by severity, flagging what to fix before submitting (blocking issues + dead code) vs what to leave for the actual review. Report-only — does not edit files.

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

Write unit and E2E tests for Grafana frontend code (React/TypeScript, any package or feature area) to the conventions this repo expects. Use when adding, backfilling, or reviewing frontend tests; when a test only asserts "it rendered" or "it's defined"; when reviewing AI-generated tests for slop; or when a frontend test is flaky. For visualization panels and grafana-ui viz components specifically, also load the `panel-testing-strategy` skill.

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

Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, commands, or another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Requires HERDR_ENV=1.

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

Use whenever the user wants to find, shortlist, vet, or enrich US marketing agencies — including branding, content marketing, PPC/paid media, social media, email marketing, performance/demand-gen, video production, and full-service digital agencies. Triggers on requests like "shortlist three B2B branding agencies in California", "find a PPC shop with ecommerce experience", "we need a content marketing partner for a SaaS launch", or "pull contact info for these 12 agency domains", even when the need is described indirectly. Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings, and third-party listings. Skip SEO-only asks (use find-seo-agency), web/software-development asks (use find-web-developer or find-software-developer), recruiting an in-house marketing hire, "write me a marketing plan" do-the-work asks, non-US firms, individual freelancers, marketing-software-product recommendations, and consumer/personal-brand asks.

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

Use whenever the user wants to find, shortlist, vet, or enrich US B2B law firms — corporate, IP/patent, M&A and securities, employment, commercial litigation, regulatory/compliance, data privacy/cyber, real estate, and tax. Triggers on "find three boutique IP law firms in California", "shortlist M&A counsel for a Series-B fundraise", "patent prosecution for our hardware startup", or "pull contact info for these 10 law firm domains", even when described indirectly (outside counsel, cap-table review, GDPR/SOC2 oversight). Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings. Skip personal/consumer legal services where the user is the end client (divorce, personal injury, criminal defense, family law, estate planning, wills) — the catalog is B2B-only. Also skip in-house GC hires, "is this NDA enforceable" DIY questions, non-US firms, individual freelancers.

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

Read a Facebook Page and its audience from real data. Pull any Page's public stats (yours or a competitor's): followers, likes, categories, intro, websites. And pull the commenters on a public Page post, since Facebook hides the reactor and liker roster and shows counts only, so commenters are the signal. Powered by Apify, no login. Triggers on "analyze my Page", "competitor Page stats", "who is commenting", "read the comments", "audience insights". Not for writing Page posts (use fb-post-writer).

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

Implement current or given task plan, optionally as an implementation draft attachment only. Use when the user calls to "implement", "realize", "draft", "dry-run", or "test-drive" the "task", "plan", "spec", or "specification".

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

Shorten a document toward a target length, given as either `--chars <N>` or `--words <N>`: first tighten the sentences, then drop low-value content, then compress the remaining content into shorter expressions -- each stage entered only while the target is still not met. Use when the user wants to "shorten", "cut down", or "reduce the length of" a document.

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

西瓜视频（Xigua）公开视频数据查询与内容分析 skill，通过 MaxHub API 查询视频详情、作者、评论、搜索、推荐和相关视频。适合长视频/中视频选题、作者画像、互动分析、热点跟踪和内容复盘。默认 read-only；agent 应按 recipes 匹配视频详情、评论、作者、搜索等意图，并通过字段流传递 item_id/video_id/user_id。所有请求发送到 https://www.aconfig.cn。

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

今日头条（Toutiao）内容数据查询与资讯分析 skill，通过 MaxHub API 查询文章/视频详情、评论、用户/媒体号、搜索、热榜和推荐内容。适合资讯选题、舆情监控、内容互动分析、媒体号画像和热点跟踪。默认 read-only；agent 应按 recipes 匹配文章、评论、搜索、热榜等意图，并用字段流字典传递 item_id/group_id/user_id 等参数。所有请求发送到 https://www.aconfig.cn。

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

知乎（Zhihu）公开内容与用户数据分析 skill，通过 MaxHub API 查询问题、回答、文章、专栏、评论、热榜、搜索和用户画像。适合问答内容研究、KOL 分析、舆情监控、选题挖掘和营销洞察。默认 read-only；agent 应按 recipes 选择问题/回答/文章/用户/搜索链路，正确传递 question_id/answer_id/article_id/url_token 等参数，避免混用 ID。所有请求发送到 https://www.aconfig.cn。

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

YouTube 公开视频与频道数据分析 skill，通过 MaxHub API 查询视频详情、评论、字幕、播放/流信息、频道资料、频道视频/Shorts/帖子、搜索、趋势和相关视频。适合海外视频研究、频道画像、字幕语料、评论分析、内容选题和竞品监控。默认 read-only；播放/下载相关信息需遵守版权与平台规则，agent 应优先走 recipes 并按 video_id/channel_id/keyword 字段流链式调用。所有请求发送到 https://www.aconfig.cn。

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

Lemon8 内容与用户公开数据分析 skill，通过 MaxHub API 查询笔记/帖子详情、评论、用户资料、搜索与推荐内容。适合生活方式内容研究、种草笔记分析、创作者画像、话题趋势和竞品监控。默认 read-only；agent 应从 recipes/_index.md 匹配用户意图，再按 recipe 详情传递 post_id/user_id/keyword 等参数。所有请求发送到 https://www.aconfig.cn。

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

Twitter/X 公开社交数据查询与传播分析 skill，通过 MaxHub API 查询推文、回复、用户资料、关注/粉丝、搜索、趋势和相关互动。适合舆情监测、账号画像、话题传播、竞品研究和内容分析。默认 read-only；agent 应优先使用 recipes，按 tweet_id/user_id/username/query 等字段流链式调用，并对个人社交数据与 UGC 做最小化处理。所有请求发送到 https://www.aconfig.cn。

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

Reddit 公开社区数据查询与讨论分析 skill，通过 MaxHub API 查询 subreddit、帖子详情、评论树、用户资料、搜索、热门/趋势内容等。适合社区舆情、话题研究、竞品反馈收集、内容洞察和用户讨论分析。默认 read-only；agent 应优先使用 recipes 串联 subreddit/post/comment/user 相关端点，并显式处理评论/UGC 中的个人信息和敏感内容。所有请求发送到 https://www.aconfig.cn。

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

快手（Kuaishou）公开数据查询与短视频分析 skill，通过 MaxHub API 查询作品详情、作者主页、评论、搜索、热榜、直播和相关内容。适合快手内容选题、达人分析、作品互动追踪、热门趋势监控和运营复盘。默认 read-only；agent 应按 recipes 选择单次或链式调用，使用字段流字典传递 photo_id/user_id 等参数，禁止自行拼接路径或猜测参数。所有请求发送到 https://www.aconfig.cn。

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

Instagram 公开社交数据查询与内容分析 skill，通过 MaxHub API 查询帖子/Reels/Stories/Highlights、评论、点赞列表、用户资料、粉丝/关注、搜索、标签和相关内容。适合海外社媒运营、KOL 画像、内容互动分析、竞品跟踪和趋势研究。默认 read-only，侧重公开或用户授权范围内的数据；agent 应优先使用 recipes 进行单端点或链式调用，并避免采集超出用户授权的个人信息。所有请求发送到 https://www.aconfig.cn。

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

小红书（Xiaohongshu/RED）公开笔记与用户数据分析 skill，通过 MaxHub API 查询笔记详情、评论、用户资料、搜索、话题、商品/种草内容、推荐流与蒲公英（PGY）创作者商业化数据。适合品牌种草分析、KOL 画像、内容选题、竞品监控、评论洞察与蒲公英博主选号。默认 read-only；PGY 域为 POST 写入式查询（high risk），调用前需用户显式确认；agent 应按 recipes 选择笔记/用户/搜索/评论/PGY 链路，使用 note_id/user_id/keyword/brand_user_id 等字段流传参，并避免采集超出授权的个人数据。所有请求发送到 https://www.aconfig.cn。

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

微博（Weibo）公开社交数据查询与热点分析 skill，通过 MaxHub API 查询微博内容、评论、转发、用户资料、粉丝/关注、搜索、热搜、话题和榜单。适合舆情监测、热点追踪、KOL 画像、内容传播分析和竞品研究。默认 read-only；agent 应优先使用 recipes 串联搜索→微博详情→评论/用户画像等流程，避免自行猜测 mid/uid/container_id 参数。所有请求发送到 https://www.aconfig.cn。

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