Is Company Deep Research safe and trustworthy?

tashan scores Company Deep Research on public evidence — it is currently active. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Company Deep Research?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Company Deep Research?

3 GitHub contributors, source: NicT89/gtm-os.

‹ The Index

Company Deep Research

skill

Author’s activation text, quoted as published

Deep-research any company end to end and produce a sourced report: site sweep, funding and M&A history, GTM org map, named customers, partner taxonomy, competitors, and public code footprint. Use when the user says "deep research [company]", "run company-deep-research", "research this company", "do a full workup on [company]", "who are their customers", "who do they partner with", "who are their competitors", "what is their tech stack", "map their GTM org", "how big is their sales team", shares a company URL and asks what the company actually does, or when jd-intake or gtm-signal-scan leaves Unknown template fields that extended search can close. …

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Install (Claude Code):

cp -r company-deep-research ~/.claude/skills/

Adoption: 1 repos
Upkeep: 100.0
Freshness: 100.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 3
License: NOASSERTION

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

Its own instructions

Its SKILL.md says when to use it, covers setup and states a limitation.

Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Pro adds the history to tashan doctor, so a run over your own config says which of yours gained an advisory, started running an install script, or lost its last maintainer — and what to move to.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

source ↗ · skill:NicT89/company-deep-research

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-12 · scorer s5 · how · something wrong here?