mcpbeat Sign in

Grad Ant Agent Skill

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'.

4k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
223
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-ant

What comes with it

9 436 bytes besides the instruction
examples/sample_scenario.md

The instruction itself

13 sections, as written by the author

Actor-Network Theory (ANT)

Overview

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.

When to Use

  • Mapping how a technology, innovation, or practice became accepted (or failed)
  • Analyzing the role of artifacts, standards, or devices in stabilizing social arrangements
  • Tracing controversy and network-building in science and technology
  • Understanding why a seemingly good innovation failed to gain adoption

When NOT to Use

  • When the analysis requires strong normative judgments (ANT is descriptive, not prescriptive)
  • When macro-level structural explanations are needed (ANT resists pre-given social categories)
  • When non-human agency is irrelevant to the research question

Assumptions

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:

  • Generalized symmetry — human and non-human actors are described in the same analytical terms
  • No a priori distinctions between the social, technical, and natural
  • Networks are the unit of analysis, not individuals or structures
  • Stability is an achievement, not a given — networks require continuous maintenance

Methodology

Step 1: Identify the Controversy or Innovation

Select the phenomenon to trace. Follow the actors — do not impose pre-existing categories.

Step 2: Map the Actants

List all relevant human and non-human actors (people, organizations, technologies, documents, standards, natural entities) involved in the network.

Step 3: Trace the Four Moments of Translation (Callon, 1986)

| 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 |

Step 4: Assess Network Stability

Evaluate whether the network holds, noting points of resistance, betrayal, or dissolution.

Output Format

## 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]

Gotchas

  • Do NOT treat non-humans as mere "context" — they must have equal analytical weight
  • ANT does not explain WHY networks form; it describes HOW they form
  • Avoid "network" as metaphor — in ANT, networks are traced empirically, not assumed
  • The researcher must "follow the actors" rather than impose categories from above
  • ANT has been criticized for lacking normative power — pair with critical theory if evaluation is needed
  • Black-boxing occurs when a network becomes so stable its internal workings become invisible

References

  • Callon, M. (1986). Some elements of a sociology of translation. In J. Law (Ed.), *Power, Action and Belief* (pp. 196-233). Routledge.
  • Latour, B. (2005). *Reassembling the Social: An Introduction to Actor-Network-Theory*. Oxford University Press.
  • Law, J. (1992). Notes on the theory of the actor-network. *Systems Practice*, 5(4), 379-393.

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

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.

4k tokens
Changelog Generator
by frostant
×9

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.

774 tokens
Test Driven Development
by w95
×7

Use when implementing any feature or bugfix, before writing implementation code

2k tokens
Writing Plans
by ZhanlinCui
×4

Use when you have a spec or requirements for a multi-step task, before touching code

816 tokens
Writing Skills
by ZhanlinCui
×4

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts
Crafting Effective Readmes
by softaworks
×3

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

15k tokens
Humanizer
by softaworks
×3

| 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.

6k tokens
Opentrons Integration
by christophacham
×3

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.

9k tokens scripts

How to use it

Copy the folder

Take asgard-ai-platform/grad-ant from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.