Menu
Generate and evaluate candidate names for a concept, pattern, or unnamed thing. Assesses cognitive load, precision, resonance, and load-bearing quality.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | name |
| description | Generate and evaluate candidate names for a concept, pattern, or unnamed thing. Assesses cognitive load, precision, resonance, and load-bearing quality. |
| argument-hint | ["concept or thing to name"] |
| user-invocable | true |
Name this concept: $ARGUMENTS
Before naming, understand what needs naming:
Produce 3-5 candidate names. For each:
Draw from multiple sources: metaphor, etymology, analogy, compression, existing domain vocabulary.
Score each name against four criteria:
Cognitive Load — Is it easy to remember, spell, pronounce, and use in conversation? Short names with clear pronunciation win.
Precision — Does it distinguish this thing from related things? A good name makes the wrong usage feel wrong.
Load-Bearing — If you deleted this name, would communication break down? Would people reinvent it? Load-bearing names are essential; decorative names are overhead.
Resonance — Does it evoke the right mental model? Does it connect to existing intuitions? A resonant name teaches you something about the thing just by hearing it.
Does this new name replace any existing names? Naming creates ontology — check what this name implies about the existing naming structure:
## Naming: [Concept]
### Candidates
1. **[name]** — [metaphor/etymology]. Evokes: [mental model].
2. **[name]** — [metaphor/etymology]. Evokes: [mental model].
3. **[name]** — [metaphor/etymology]. Evokes: [mental model].
### Evaluation
| Name | Cognitive Load | Precision | Load-Bearing | Resonance |
|---|---|---|---|---|
| [name] | [low/med/high] | [low/med/high] | [yes/no] | [low/med/high] |
### Recommendation
**[name]** (confidence: high/medium/low)
Rationale: [why this name wins]
### Load-Bearing?
[Yes/No] — [Would communication break without this name?]
### Retirements
[Existing names this replaces, if any, and why]
### Ontology Note
[How this name relates to the existing naming structure]
Source and independently verify candidates for a role from a job description URL. Runs the source-candidates workflow (Webset creation → Exa verification of every claim → validated/rejected CSVs). Use whenever the user wants to find candidates, source people for a role, run a recruiting search from a job posting, or invokes /source-candidates.
Verify a webset item's enrichments against public data using independent Exa searches. Returns structured verdict with confidence score, evidence, and discrepancies. Use when a channel event or workflow step requires enrichment verification before proceeding.
Produce uniform, verified background reviews / biographies / profiles for a SHORTLIST of entities (people or companies) by dispatching one research subagent per entity in parallel, then synthesizing and persisting the results. Use when the user asks for "bios", "background reviews", "profiles", "tell me about each of these", or a comparison across several candidates — especially after a [[websets-secondary-review]] produced a shortlist. For a single entity use [[deep-research-item]] instead; this is the parallel, many-entities harness.
Run comprehensive research on an entity — news, funding, tech stack, buyer mapping, angle building. Writes findings to the webset store and optionally to Airtable. Use after verification passes or when a channel event requires deep research on a specific entity.
View, add, modify, or remove per-source workflow configurations. These configs control how channel events are routed to workflow chains. Manages data/workflow-configs.json.
Build Claude Code Channels — MCP servers that push events into a live Claude Code session so Claude can react to things happening outside the terminal. Use this skill whenever the user wants to: build a custom channel server, push webhooks/CI alerts/monitoring events into Claude Code, build a two-way chat bridge (Telegram, Discord, or custom), relay tool-use permission prompts remotely, understand the channel notification protocol, declare the claude/channel or claude/channel/permission capability, wire up sender gating/allowlists, or package a channel as a plugin. Trigger on any mention of Channels, channel MCP, push events to Claude Code, Claude Code from phone, or remote control Claude Code.