From investigator
Structured overview of a named individual's public presence: professional history, news coverage, academic work, people search aggregators, and company affiliations. Requires a complete authorisation gate before starting.
npx claudepluginhub hpsgd/turtlestack --plugin investigatorThis skill is limited to using the following tools:
Produce a structured overview of $ARGUMENTS's public presence.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.
Produce a structured overview of $ARGUMENTS's public presence.
[!IMPORTANT] This skill requires the investigator agent's full authorisation gate before it can be invoked. Do not run this skill without a logged gate record (authorisation, purpose, scope, subject awareness). The gate is not optional.
Search LinkedIn public profile, company website bios, and professional registrations.
For professionals in regulated fields, check licensing boards:
Search Google News (site:news.google.com "[name]") and relevant industry press for the subject's name combined with professional context.
For older coverage: newspaper archives where accessible.
Note: for names with many homonyms, add qualifiers (employer, location, field) to all searches.
For researchers, academics, or published professionals:
Note publication count, citation count (very rough proxy for influence in field), and institutional affiliations.
These aggregate public records — use for confirmation, not as primary source.
US-based subjects:
AU-based subjects:
Note: AU/NZ have no equivalent of the comprehensive US people-search aggregators. These directories are narrower and less cross-referenced — use for directory-style confirmation only.
NZ-based subjects:
Check for current and historical directorships or company registrations:
Before including any fact in the output, confirm it across at least two independent sources. A single people search result is a lead, not a finding.
Flag single-source findings explicitly.
A complete background check typically needs both this skill and /investigator:public-records — this skill covers professional history and licensing, public-records covers court filings and company directorships. Run both unless the gate scope explicitly limits to one.
If a company affiliation is found and the investigation scope includes the organisation, hand off to /investigator:entity-footprint (digital presence) or /investigator:corporate-ownership (ownership structure).
### People lookup: [Name]
**Gate record:** [link or copy of gate record from investigator]
**Context anchors used:** [employer, location, field — what was used to disambiguate]
#### Professional history
[Roles, employers, tenure — sourced]
#### Licensing and registrations
[Any professional registrations found — or "none found in checked registries"]
#### News and press
[Dated list, most recent first — or "no significant press coverage found"]
#### Academic/published work
[Publication summary — or "no published work found"]
#### Company affiliations
[Directorships or company registrations found — or "none found"]
#### Source cross-reference
[Which key facts confirmed across 2+ independent sources; which are single-source only]
#### Gaps and limitations
[What couldn't be confirmed; what is out of scope per gate]