1,161 件 ・ 関連度順
概要と使いどころ
Mine Claude Code session data for analytics — token usage, tool rankings, skill invocations, session search, and prompt history. Use when asked about session stats, token costs, tool frequency, skill usage patterns, or finding past sessions by prompt text.
日本語の概要は準備中です。原文の説明を表示しています。
Mine a codebase for breakthrough, evidence-backed opportunities — features, additions, refactors, simplifications, DX, UX, reliability, performance, or architecture cleanup. Researches project reality first, then forces two escalation gates (reject the merely-adequate idea; expand ambition 10x then collapse to the smallest proof-bearing artifact). Outputs ranked opportunities, an escalation ledger, and one plan seed. Does not implement or create tickets.
日本語の概要は準備中です。原文の説明を表示しています。
Mitigate incidental code complexity when control flow is tangled, nesting is deep, names are hard to parse, or reasoning requires cross-file hops. Use when a review stalls on readability, you need an analysis-first refactor plan before edits, or you want essential-vs-incidental verdicts, ranked simplification steps, a small structural sketch, and a TRACE assessment (analysis-only; no edits).
日本語の概要は準備中です。原文の説明を表示しています。
Load when evaluating an Islamic software feature, provider policy, AI behavior, moderation, monetization, privacy, defaults, ranking, self-hosting, or deployment model for provider responsibility and Islamic value-sensitive design; not for generic fiqh rulings or ordinary technical implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the FAA System Safety Handbook (Dec 30, 2000). Use for system safety as a specialty within systems engineering: the five-step safety risk management process (mandated by FAA Order 8040.4 and the AMS), the severity-by-likelihood risk matrix and acceptance bands, the Safety Order of Precedence, system-description models (5M, SHEL(L)), the hazard-analysis activities (PHL/PHA/RHA/SSHA/SHA/O&SHA/HHA), integrated system hazard analysis, the analysis techniques (FTA, FMEA/FMECA, Fault Hazard, Common Cause, Sneak Circuit, Energy Trace), closed-loop hazard tracking (Safety Action Record), and the specialty domains the handbook covers — acquisition-lifecycle safety and contracting (OSA/CSA/SSPP/ISSPP), software safety (control-capability ranking, SHCM, DO-178B), test & evaluation safety, facilities safety, commercial launch safety (AST licensing, expected casualty, MPL/DAMP), system safety training, and Operational Risk Management (ORM) with human/organizational factors. Scope limits: this is a year-2000 FAA how-to; it predates the modern FAA/ICAO Safety Management System (SMS) and Just Culture regulatory frameworks, and many cited orders, advisory circulars, and launch-licensing rules have since been restructured. It is FAA/NAS-centric, leans on MIL-STD-882C, and does not define the SE life-cycle processes themselves (use nasa-npr-7123 / dau-se-guidebook) or reproduce third-party standard text (MIL-STD-882, DO-178B, ISO/IEC/IEEE).
日本語の概要は準備中です。原文の説明を表示しています。
Synthesises training survey responses and manager notes into a DRAFT training needs report by role: coded needs with record counts per role (n of N), the evidence type behind each count, anonymised quotes cited to record codes, disagreements between what staff report and what managers observe, gaps where a role is under-represented or a required skill has no evidence, and follow-up questions to settle before any course is designed. Never rates an individual, ranks a team or turns a count into a competence verdict. Use when the user asks to "analyse this training survey", "what training do our teams need", "summarise the manager feedback on skills gaps", "build a training needs analysis by role" or "which roles have the biggest skill gaps". Do not use for turning an agreed need into a course, use course-outline-builder instead; for exit interviews, use exit-interview-synthesis. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Builds and maintains a DRAFT impact log from notes, messages, status updates and completed work: one row per outcome with its evidence and evidence level, date, who benefited and the source it traces to, plus a gap list of outcomes that still lack evidence, structured so a later review, appraisal or promotion case can draw on it. Use when the user asks to "start an impact log", "add this to my impact log", "log what I achieved this quarter", "pull my wins out of these notes", "turn these messages into evidence for my review" or "what do I have evidence for so far". Do not use for a performance rating, ranking, pay or promotion decision, the skill records evidence and never judges it; for the review narrative itself, use performance-review-drafter; for a role profile built from the work, use job-description-drafter instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Reads two or more supplier, bid or tender responses against a requirements list and returns a DRAFT comparison pack: a requirement-by-supplier matrix, gaps per supplier, clarification questions and neutral observations, for an evaluation panel. Never scores, weights, ranks or recommends a winner; the award stays with the panel. Use when the user asks to "compare these bids", "matrix the tender responses against our requirements", "collate the RFQ replies", "show me where each supplier falls short" or "draft clarification questions for the bidders". Do not use for scoring or weighting against agreed criteria, use supplier-evaluation-matrix instead, or for writing the requirements, use rfp-requirements-pack instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts a DRAFT self-assessment, peer feedback note or manager review narrative from the evidence the writer supplies (goals, examples, metrics, notes), in the review template where given: every sentence tied to a numbered evidence item, unsupported claims removed and logged, and a gaps list to complete before submitting. Never assigns, suggests or implies a rating, score, ranking, pay or promotion outcome. Use when the user asks to "write my self-assessment", "draft peer feedback for a colleague", "turn these notes into a performance review", "help me write the year-end review for my report", "summarise my achievements against my goals" or "draft the mid-year review". Do not use for a job description or role profile, use job-description-drafter instead; for a new hire's first 90 days, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Turns an actuals-versus-budget extract (spreadsheet, export or pasted table) into a DRAFT variance table with absolute and percentage variances, favourable or adverse marking and a ranking by size, then drafts plain-language driver hypotheses for each material variance as questions to verify with a named owner, never as asserted causes. Use when the user asks to "explain these variances", "why are we over budget on this line", "write the variance commentary for the management pack", "actuals versus budget analysis" or "which lines drive the variance". Do not use for a dataset with no budget or comparison column, use dataset-insight-pack instead; for weekly operational figures against last week, use kpi-weekly-report-writer. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Triage a lead pipeline and say who needs action today: replied means send the scheduling link, link sent 24h ago without a booking means nudge, awaiting reply means check inbound, going cold means follow up, booked means close out. Ranked and draft-first, so the owner edits before anything goes out. Triggers: "/pipeline", "work my leads", "who is stuck in the funnel".
日本語の概要は準備中です。原文の説明を表示しています。
After shipping a repo, release or feature, find who on GitHub actually needs it: search issues, discussions and catalogs for the symptom, rank live threads and draft one precise reply per consumer. Use right after any artifact goes public. Triggers: /consumer-hunt, /ch, find consumers, where to submit.
日本語の概要は準備中です。原文の説明を表示しています。
Ask the second brain in plain words: semantic search over the curated vault with embeddings plus a reranker, returning the smallest relevant slice instead of a corpus dump. Token-cheap. Triggers: "/ask <question>", "what do I have on <topic>", "what did I write about X".
日本語の概要は準備中です。原文の説明を表示しています。
Show the operator's day: today's calendar plus what needs them personally (leads due, people awaiting a reply, deadlines), pulled from Calendar and Telegram and ranked. Read-only: sends and commits nothing. Triggers: "/agenda", "what's on today", "my agenda".
日本語の概要は準備中です。原文の説明を表示しています。
Author and validate nvoos-chart fenced-JSON chart blocks for NV oOS chat surfaces — 29 chart types across distribution, part-to-whole, ranking, change, special and grid families. Covers type selection, the v2 schema (values/series/data.items, mode, sort, direction, unit, animate, table, target), data-shape rules, the create_chart_fence server validator, the a11y checklist, and copy-paste JSON templates. Use when writing chart fences in assistant responses, choosing a chart type for data, validating chart JSON, or deciding between nvoos-chart, create_chart, generate_chart and generate_mermaid.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "find trending topics", "what trends should my brand jump on", or "time a campaign around a cultural moment"; produces a ranked trend report with brand-fit scores, format calls (rising/peak/declining), a cultural calendar, and go/skip recommendations. Not for finding the creators to run those trends — use influencer-discovery; not for building the brand posting calendar from a go verdict — use social-calendar-builder. 热点趋势洞察/借势营销
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "analyze the SERP" or "SERP分析"; maps SERP features, layout, ranking factors, search intent, AI Overviews, and snippet opportunities for a query. Not for keyword demand discovery — use keyword-research. SERP分析/搜索结果
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "monitor brand mentions", "set up social listening", "did anything spike about us this week", or "watch these accounts for buying triggers"; runs always-on keyless listening — a versioned listening-query architecture (brand variants incl. misspellings and 中文 names, exclusion terms, per-source syntax for HN Algolia / Bluesky / GDELT / Tavily), a mention sweep with six-class triage (crisis / bug / lead / praise / question / spam) each routed with an SLA, a 7-day rolling baseline with spike flags (the crisis trigger input), a B2B trigger watchlist (funding / hiring / launch signals), and an explicit coverage disclosure where X/IG/TikTok/LinkedIn/小红书 numbers are proxy-labeled, never Measured. Not for launch-window telemetry (T-0→T+30 rank and review polling) — use launch-monitor. 舆情监听/品牌提及监测/基线突刺/触发信号
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "analyze backlinks", "analyze my off-site signals", or "track AI traffic / ChatGPT / Perplexity referrals"; profiles referring domains, anchor-text mix, toxic links, and disavow candidates (backlinks mode) or isolates AI-assistant referral sessions in GA4/GSC/logs and reports their trend, landing pages, and AI-vs-organic conversion (ai-referrals mode). Not for internal links — use site-structure-optimizer; not for keyword positions — use rank-tracker; not for multi-metric stakeholder reports — use performance-monitor. 外链分析/反向链接/AI流量/AI引荐/ChatGPT流量/AI转化
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "build programmatic SEO pages", "generate pages at scale", "rank on a high-authority third-party site", "borrow domain authority", "build a vs / alternative page", "do local SEO", "optimize a Google Business Profile", or "fix NAP" — one page-build router with four modes: programmatic (template × dataset systems), parasite (barnacle publishing on Medium/Reddit/LinkedIn/GitHub), comparison (vs / alternative pages in four formats), and local (GBP + NAP + citations + location pages), each with its own thin/duplicate, honesty, or reputation-abuse guardrail. Not for finding what to target — use keyword-research or content-gap-analysis; not for drafting one standalone article — use content-writer; not for scoring a page for publish — use content-quality-auditor. 程序化SEO/批量页面/寄生SEO/借势权重/对比页/vs页/替代页/本地SEO/谷歌商家档案/NAP一致性
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "find influencers", "build an influencer list", or "discover creators in [niche]"; produces a multi-platform candidate pool, per-influencer profiles, authenticity red-flag screening, and a tiered shortlist with preliminary triage signals. Not for STAR scoring or ranking a known shortlist — use fit-scorer. 达人挖掘/找达人/创作者名单
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "write the email", "draft subject lines", or "build email creative"; produces the pre-click unit — subject-line variants + preheader, body copy, one clear CTA, and a plain-text alt — message-matched to the destination page and claims-ledger-aware. Not for pre-scoring or ranking subject-line variants (spam/truncation/render pre-score) — use subject-line-lab; not for scoring the email or computing EQS — use email-quality-auditor; not for the multi-step flow — use email-sequence-designer; not for the A/B test plan — use send-experiment-designer. 邮件文案/主题行/邮件创意
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end SEO operations for B2B SaaS organic visibility. Use this skill when you need keyword research, technical SEO audits, content optimization, link building strategy, international expansion, AI/AEO optimization, schema markup, Core Web Vitals improvements, and organic traffic growth planning. Also triggers on: SEO, keyword research, technical SEO, link building, content optimization, international SEO, hreflang, x-default, multilingual site, translated pages not ranking, our German site gets no traffic, language switcher, auto-redirect by country, machine translation SEO, content parity, ccTLD vs subfolder, AI search, AEO, GEO, Core Web Vitals, schema markup, organic traffic, G2 listing, Capterra, TrustRadius, review-platform category page, best software roundup, listicle placement, directory submissions, do we need a Google Business Profile in [country], local SEO with no office, Google Business Profile eligibility, virtual office address SEO, coworking address business profile, business profile suspended, NAP consistency, local citations for SaaS, LocalBusiness schema.
日本語の概要は準備中です。原文の説明を表示しています。