From valency
Use when the user asks about a researcher's collaborators, co-authors, research network, wants to map who works with whom, or wants to see how a researcher's focus has diverged from their collaborators. Triggers on questions like 'who does X collaborate with', 'show me X's network', 'find connections between researchers', or 'how has X's work drifted from their coauthors'. Also invokable as /valency:network <author_name>.
How this skill is triggered — by the user, by Claude, or both
Slash command
/valency:networkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Map a researcher's collaboration network.
Map a researcher's collaboration network.
The user provides an author name (e.g., "Yoshua Bengio").
Call get_author_profile with:
author (string): the author nameIf no results are found, tell the user the author was not found and suggest checking the spelling. Stop here.
Note the author's top categories from this result — you'll need them to identify cross-domain bridges.
Call find_coauthors with:
author (string): the author namelimit (integer): 20This returns collaborators ranked by co-publication count. Note the top 5 collaborators for the next step. Use the coauthor_norm field (normalized name) when passing names to subsequent tool calls.
For each of the top 5 collaborators from Step 2, call find_coauthors with:
author (string): the collaborator's normalized name (coauthor_norm)limit (integer): 10Collect all second-degree collaborators. Remove any that are already direct collaborators of the focal author (from Step 2) or the focal author themselves.
Call compare_authors with:
authors (array of strings): a JSON array containing the focal author name and up to 4 of their top collaborators (max 5 total, tool requires 2-10), e.g. ["Yoshua Bengio", "Ian Goodfellow", "Aaron Courville"]This returns side-by-side profiles with category overlap information. The result also gives you everything you need to compute divergence: each author's category distribution as a list of {category, count} pairs, plus a shared_categories array.
For each top collaborator from Step 4, compute a divergence characterization from the compare_authors result. For each collaborator, determine:
Synthesize these into a one-sentence characterization per collaborator. Examples:
A brief paragraph:
A table of collaborators from Step 2 (top 10):
| Collaborator | Co-authored papers | Primary domain |
|---|---|---|
| Name | 15 | cs.LG |
| ... | ... | ... |
The "Primary domain" column comes from Step 4 comparison data for the top collaborators. For collaborators not included in the comparison, omit the domain or mark as "—".
A list of notable second-degree connections from Step 3 — people who collaborate with the focal author's collaborators but not directly with the focal author. Show up to 10, prioritizing those who appear via multiple collaborators:
Highlight collaborators from Step 2 whose primary domain (from Step 4) differs from the focal author's primary domain. These represent interdisciplinary connections:
If no cross-domain collaborators are found, note that the author's network is concentrated within their primary domain.
For each top collaborator compared in Step 4, present the divergence characterization computed in Step 5. Use this format:
Collaborator Name (N shared papers)
If all top collaborators have nearly-identical category distributions and timelines, note that the network is intellectually homogeneous and divergence analysis is uninformative — but still show the table for completeness.
The point of this section is to make visible how the focal author's intellectual position has drifted relative to their closest collaborators. Lead with the most divergent collaborator, not the most-collaborated-with one.
/valency:profile <collaborator> — for any interesting collaborator/valency:network <collaborator> — to explore a collaborator's own network/valency:similar <paper_id> — for co-authored papers of interestCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub valency-oss/valency-claude-plugin --plugin valency