Claude
Skill
entity-research
Research companies and people - leadership, revenue signals, tech stack, contacts, and sources. Use for sales intel, partner diligence, or competitive briefs.
Virus-scanned
Reviewed automatically before listing.
Download
navinspire-ia-navin-navin_skills_entity-research-e9c73a3.zip · 0 KB
Install
skills CLI
npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/entity-research
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git
git clone https://github.com/Navinspire-ia/navin.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Entity & Company Research
Overview
Build a sourced company/person dossier. Separate facts from inference.
Workflow
- Confirm the entity (legal name, domain, geography).
- Gather from official site, registries, LinkedIn-like public pages, news, job posts (tech stack signals).
- Structure the dossier:
## Entity
- name / domain / HQ
## What they do
...
## People
- ...
## Signals
- revenue / funding / headcount (cite)
- tech (from jobs, engineering blog)
## Contacts / next steps
- ...
## Sources
- ...
- Mark confidence (high/med/low) per claim.
- Never invent emails or phone numbers - only cite found contacts.
Rules
- Comply with user policies on personal data.
- Prefer primary sources; label blogs as secondary.
Files (navin)
-
SKILL.md 1 KB
--- name: entity-research description: Research companies and people - leadership, revenue signals, tech stack, contacts, and sources. Use for sales intel, partner diligence, or competitive briefs. metadata: {"navin":{"emoji":"🏢","category":"navigation"}} --- # Entity & Company Research ## Overview Build a sourced company/person dossier. Separate facts from inference. ## Workflow 1. Confirm the entity (legal name, domain, geography). 2. Gather from official site, registries, LinkedIn-like public pages, news, job posts (tech stack signals). 3. Structure the dossier: ```markdown ## Entity - name / domain / HQ ## What they do ... ## People - ... ## Signals - revenue / funding / headcount (cite) - tech (from jobs, engineering blog) ## Contacts / next steps - ... ## Sources - ... ``` 4. Mark confidence (high/med/low) per claim. 5. Never invent emails or phone numbers - only cite found contacts. ## Rules - Comply with user policies on personal data. - Prefer primary sources; label blogs as secondary.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.