Apply Actor-Network Theory (Latour, Callon) to trace how human and non-human actors (actants) form networks through translation processes. Use this skill when the user needs to map sociotechnical assemblages, analyze how innovations stabilize or fail through network-building, trace the four moments of translation (problematization, interessement, enrollment, mobilization), or when they ask 'how did this technology become accepted', 'who and what holds this network together', or 'why did this innovation fail to gain traction'.
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-ant
Actor-Network Theory treats human and non-human entities symmetrically as "actants" that form networks through processes of translation. Developed by Latour, Callon, and Law, ANT traces how heterogeneous networks are assembled, stabilized, and sometimes dissolved — rejecting the a priori distinction between the social and the technical.
IRON LAW: Non-human actors have AGENCY in ANT — treating technology
as a passive tool violates the framework's core principle. If your
analysis strips agency from artifacts, you are NOT doing ANT.
Key assumptions:
Select the phenomenon to trace. Follow the actors — do not impose pre-existing categories.
List all relevant human and non-human actors (people, organizations, technologies, documents, standards, natural entities) involved in the network.
| Moment | Description |
|--------|-------------|
| Problematization | A focal actor defines the problem and positions itself as an obligatory passage point |
| Interessement | Devices and strategies lock other actors into proposed roles |
| Enrollment | Actors accept and perform their assigned roles in the network |
| Mobilization | Enrolled actors come to represent wider constituencies; the network stabilizes |
Evaluate whether the network holds, noting points of resistance, betrayal, or dissolution.
## ANT Analysis: [Context]
### Focal Actor and Problematization
- Focal actor: [who/what defines the problem]
- Obligatory passage point: [the framing that makes the focal actor indispensable]
### Actant Map
| Actant | Type | Role in Network | Interests |
|--------|------|-----------------|-----------|
| [name] | [human/non-human] | [role] | [what they want] |
### Translation Process
1. **Problematization**: [how the problem was defined]
2. **Interessement**: [devices used to lock actors in]
3. **Enrollment**: [how actors accepted roles]
4. **Mobilization**: [how representatives stood for wider groups]
### Network Stability Assessment
- Stabilizing factors: ...
- Points of fragility: ...
- Black boxes formed: ...
### Implications
1. [Key insight about the network]
2. [What would happen if key actants were removed]
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take asgard-ai-platform/grad-ant from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.