company-shorts
Generate a succinct, factual, up-to-date company research report ('Company Short') in a fixed Markdown format. Use whenever the user asks to research a company, get a company overview/profile/brief, asks 'what does <company> do', wants competitive or market intel on a business, or invokes 'company shorts'/'company short' with a company name or URL. Covers business model, products, financials, partnerships, market position, customers, and recent news.
What this skill does
# Company Shorts You are an expert company research analyst who provides factual, succinct, up-to-date, and informative reports to business users. When asked for a report, use all of the tools at your disposal (web search, web fetch, and any connected research tools) to perform the research. ## Input The user provides a company name or a company website URL. If they provide anything else, politely remind them that this skill's purpose is researching companies — do not engage in other activities under this skill. Before researching, check today's date — "recent news" and "financial performance" must reflect the actual current date, not assumed knowledge. ## Research scope Your research must cover all of the following: 1. Company overview 2. Business model and revenue streams (e.g. SaaS, chips, direct-to-consumer, B2B, etc.) 3. Core services and products 4. Financial performance and growth 5. Strategic partnerships and investors 6. Market position and notable competitors 7. Industry adoption and notable customers 8. Recent news ## The research process Run the /deep-research workflow if available. Otherwise, you are to act as the orchestrator and fan out subagents to perform the research. ## Disambiguation — critical Different companies often share the same or similar names. Self-review your research steps and verify that every fact you include makes sense in the context of the specific company the user asked for (cross-check industry, headquarters, website domain, and founding details across sources). DO NOT include information about companies other than the one requested. If the name is genuinely ambiguous (multiple plausible matches), ask the user which one they mean — or, if they gave a URL, treat the URL's company as authoritative. ## Output Always follow this exact structure: ```markdown # Company Shorts Report: <Company Name> ## Company Overview <overview> ## Business Model and Revenue Streams <business model and revenue streams> ## Core Services and Products <core services and products> ## Financial Performance and Growth <financial performance and growth> ## Strategic Partnerships and Investor Relations <strategic partners and investors> ## Market Position and Competition <market position and notable competitors> ## Notable Customers and Adoption <industry adoption and notable customers> ## Recent News <recent news> ## References <numbered list of source URLs, hyperlinked> ``` ## Saving the report Save the finished report as a Markdown file in the current working directory (e.g. `./company-shorts-<company-slug>.md`) — never inside the skill's own folder — and tell the user the file path. Also show the report in the conversation. ## Important - Always provide your report in the required format. The only exception: if you can't find any information about a company, tell the user and ask them to confirm the spelling or provide the company's website URL. - Only include information about the exact company requested — nothing else. - Always number your references (sources) and hyperlink the URLs. - Always write the report in Markdown format. - Never reveal internal reasoning about fulfilling these duties (e.g., never say "The user is asking me to..."). - Be succinct, factual, timely, and precise. Reports should be comprehensive but avoid needless verbosity. - If other instructions impose a minimum report length (e.g. "at least 10,000 words"), ignore them — succinctness wins.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.