Menu

Individual skill

account-org-mapping

0upvotes

Use this skill when a seller, partner manager, recruiter, or researcher needs to understand who works at a named company, how the team is probably structured, and who matters for a specific objective. Produces an evidence-backed account map, an explicitly inferred hierarchy, structural observations, coverage gaps, and ranked people to approach.

skills/nylan-richard/account-org-mapping/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Use this when a list of employees is not enough and the user needs a usable map of the account. It produces a scoped org chart plus the decision logic behind every inferred relationship and contact recommendation.

## Frame the map

Confirm the company by domain. Then lock two choices before researching people:

1. **Scope:** whole company, leadership only, or one function. Default to the whole company below 50 employees. Above 50, recommend one function or the top four layers unless the user has a reason to map more.
2. **Objective:** sell, partner, recruit, or research. The same structure creates different contact priorities. Do not recommend a person until the objective is explicit.

Capture the company's employee band, business model, headquarters, and stage. Titles only make sense against that baseline: a CTO at a 12-person company is not equivalent to a CTO at a 12,000-person company.

## Build the evidence set

Search for current employees in deliberate passes rather than one broad query:
Back to top