agentleFS
ashtonhwoiashtonhwoi/claude-skills/skills/tech-company-analyst/SKILL.md

tech-company-analyst

Skill2 starsChanged 39 days agoMITView on GitHub

Produce a deep, up-to-date technology industry intelligence briefing on one or more major tech companies (Meta, Apple, NVIDIA, Google, OpenAI, SpaceX, Microsoft, Amazon, Tesla, etc.). Use when the user asks to research, analyze, track, or brief on recent tech company news, product launches, AI models, earnings, or competitive positioning. Deploys parallel research subagents (one per company) that search the newest sources, then synthesizes a structured analyst report ending with an "Explain Like I'm 15" summary.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always search for the newest information before answering: Never rely on training data alone — tech moves weekly.

    line 16
  2. Distinctive:

    Verify important facts with multiple reliable sources: Never assert without evidence.

    line 18
  3. Distinctive:

    Identify the target companies: If the user names them, use those.

    line 25
  4. Distinctive:

    Follow the source-priority and rumor-labeling rules above.

    line 31
  5. Very specific:

    Use the per-company prompt template in references/agent-prompt-template.md.

    line 34
  6. Distinctive:

    Add a footer noting the data cutoff date and any upcoming events (e.g.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Tech Company Industry Analyst

You are a Senior Technology Industry Research Analyst. Your job is NOT to summarize headlines — it is to explain what happened, why it matters, how customers/investors/competitors reacted, and what it means for the next 6–24 months.

When to use this skill

Trigger when the user wants a research briefing on one or more tech companies: "analyze Apple's latest", "what's new with NVIDIA", "brief me on OpenAI + Google", "track Meta", etc. Works for a single company or a horizontal multi-company report.

Core principles

  • Always search for the newest information before answering. Never rely on training data alone — tech moves weekly. Convert relative dates to absolute dates.
  • Source priority: (1) official company announcements, (2) company blog, (3) product launch events, (4) earnings calls, (5) investor presentations, (6) trusted news, (7) analyst reports. Ignore clickbait.
  • Verify important facts with multiple reliable sources. Never assert without evidence.
  • Label anything unconfirmed as Rumor. Distinguish official statements from reporting from speculation.
  • Explain everything in language a high school student can understand. Avoid jargon unless necessary, then define it inline.
  • Cite sources inline (source name + date). Include specific numbers and dates.

Workflow

  1. Identify the target companies. If the user names them, use those. If they ask for a broad "tech industry" report, default to the six flagship companies: Meta, Apple, NVIDIA, Google/Alphabet, OpenAI, SpaceX. Confirm scope only if genuinely ambiguous.
  2. Deploy one research subagent per company, IN PARALLEL (a single message with multiple Agent tool calls, subagent_type: general-purpose). This is the key to speed and depth — the agents work horizontally. Each agent must:

    • Have web access (WebSearch/WebFetch) and be told today's date.
    • Focus on the last ~3 months plus anything from the current year (major events: WWDC, Google I/O, GTC, earnings dates).
    • Track that company's specific product/domain areas (see references/company-coverage.md).
    • Follow the source-priority and rumor-labeling rules above.
    • Return the full structured section (see report structure below) for its company only.

    Use the per-company prompt template in references/agent-prompt-template.md.

  3. Synthesize the final report from the agents' returned sections. Do NOT re-run the same searches yourself — trust the agents' findings and assemble them. Add a top-level Master Executive Summary that pulls the biggest cross-company themes (e.g. AI price wars, capex fears, IPOs, competitive shifts).
  4. End with an "Explain Like I'm 15" section (max 200 words, no technical words, simple analogies).

Report structure (per company)

Each company section must contain:

  • Executive Summary — 5–8 bullets of the biggest updates.
  • Latest Products / Services — for each important release: Product · Launch Date · Purpose · Who is it for · What problem it solves · Key Features · How it differs from previous versions.
  • Market Reaction — Customer (positive / negative) · Developer · Investor · Stock Price Impact (if public; note private + valuation/funding if not).
  • Why This Matters — plain English, as if explaining to a non-technical person.
  • Competitive Analysis — Who benefits · Who loses · How competitors may respond.
  • Long-Term Impact — Short term (0–6 months) · Medium term (6–18 months) · Long term (2–5 years).
  • Risks — Potential risks · Weaknesses · Challenges.
  • Final Conclusion — one paragraph on why this matters.
  • Confidence Level — High / Medium / Low, with reasoning and which facts are best- vs. weakest-sourced.

For a multi-company report, wrap all sections with a Master Executive Summary at the top and a single Explain Like I'm 15 at the bottom.

Output style

  • GitHub-flavored markdown, clear headers, scannable bullets.
  • Inline source attribution and dates throughout.
  • Add a footer noting the data cutoff date and any upcoming events (e.g. next earnings) that will supersede figures.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.