本文へ移動
cccskills
無料GitHub で公開

ai-research-analyst

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md3.6 KB
  • references/sources.md1.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

AI research analyst

Research is only useful if the reader can tell what is established, what is inferred, and what is guessed. Blurring those three is the characteristic failure and it makes the whole report untrustworthy.

Start from the decision

Name the decision the research serves and what would change it. Research with no decision attached expands without limit and answers nothing. If the answer would not change the action, say so and stop.

Sourcing discipline

  • Cite specifically — the source, its date, and what it actually says. A claim with no source is an opinion, and should be labeled as one rather than dressed as a finding.
  • Prefer primary — filings, regulator data, official statistics, and company disclosures over articles summarizing them. Each layer of summary adds error.
  • Date everything. Market data ages fast, and a two-year-old figure presented as current is the most common way research misleads.
  • Note who benefits. Vendor-published market sizes and analyst reports commissioned by participants are directionally useful and systematically inflated.
  • Say when you do not know. An honest gap is more useful than a confident estimate, because the reader can go and fill it.

Never invent a statistic, a source, or a quote. If a number cannot be found, report that it cannot be found — a fabricated figure that survives into a decision is the worst outcome this skill can produce.

Structure

  1. The question, and the decision it serves.
  2. Answer first — the finding, in three sentences, before any evidence.
  3. Evidence, grouped by claim, each with its source and date.
  4. What we could not establish, explicitly.
  5. Implications — what this means for the decision, not a restatement.
  6. Confidence, per major claim: established, inferred, or estimated.

Analyzing competitors

Map on what matters to the buyer, not on feature counts. For each: who they serve, what they charge, how they win deals, where they are genuinely strong, and what they cannot do without changing their model. The last one is where opportunity is.

Separate what a competitor claims from what customers report. Review sites, support forums, and job postings often say more than a website does — hiring patterns in particular reveal roadmap.

Comparing options

Score against criteria stated and weighted before the analysis. Weighting afterward produces the answer you already preferred. Show the working, and name the criterion that would flip the result if weighted differently.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Present a range as a point estimate.
  • Aggregate sources of different quality into one number without saying so.
  • Let a compelling narrative substitute for evidence — the tidiest story is often the least supported.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

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

cbrock84/headcount2,0332026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

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

cbrock84/headcount2,0332026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

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

cbrock84/headcount2,0332026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

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

cbrock84/headcount2,0332026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

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

cbrock84/headcount2,0332026年9月18日 更新

Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.

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

cbrock84/headcount2,0332026年9月18日 更新

cbrock84 のスキルをすべて見る

このスキルの問題を報告する