Loading...
Loading...
Found 4 Skills
Decision-grade entity research skill — produces a hypothesis-tested dossier on a specific company, person, nonprofit, or government org, not a generic profile. Forcing intake makes the user state their hypothesis upfront (what they already believe and want to verify or disprove) so the dossier tests it rather than confirms it. Output is an editable Word document (.docx) with verdict on the hypothesis, identity facts, 12-month activity timeline, network signals, reputation signals, red flags, 3-5 conversation hooks tied to specific findings, and source-provenance audit log. Uses WebSearch + WebFetch + free APIs (SEC EDGAR, GitHub, ProPublica Nonprofit Explorer) as workhorses; optional BYOK MCPs (LinkedIn, Crunchbase, Apollo, Pitchbook, SimilarWeb) enhance coverage. Triggers: 'research [company]', 'dossier on [person/company]', 'background check on [entity]', 'prep me for a meeting with [person/company]', 'due diligence on [company]', 'what should I know about [entity]', 'research [person] before I [meet/hire/invest]', 'competitor research on [company]', 'investor diligence [company]', 'interview prep for [company]'. Honors sensitivity exclusions for journalism + personal-vetting contexts.
Use for session, scoped, PR, range, full audit, simplification, and source/provenance reviews with evidence-first findings. NOT for feature implementation or benchmarking.
Answers why code is shaped as it is with an evidence-rated report, tagging each claim [Direct], [Supported], [Inferred], or [Speculative] and closing with a Sources Consulted list that covers git, PRs, tickets, docs, chat, and observability, naming the sources left unchecked. Read-only. Use when the user says "why is it built this way?", or when asked why code is shaped as it is, why a value or limit was chosen, what alternatives were rejected, or what forces shaped a decision, including when the asker offers a guess at the reason. Use it even when commits or PR text are already in context, since a plain answer from them omits the tiers and the unchecked sources. Not for how code works; use explaining-architecture.
Recovers decisions, previous fixes, research, and what followed a prompt from past AI conversations, with source evidence. Use when asked to "search past chats", "we fixed this before", "what followed this prompt", or "why did the plan change". Reads local Claude Code, Codex, Grok, and Cursor history plus explicit ChatGPT or Claude exports.