Skip to content
Development
Skill

/role-inject

Install the injector role on an ephemeral session. Distills the latest conversation delta into a self-contained directive for a running workstream. Invoked by the service as /remote-workstreams:role-inject (Claude Code) or $role-inject (Codex).

From plugin
remote-workstreams
34 skills1 command1 hook
Install
$ npx -y skills add ryan-scheinberg/remote-workstreams --skill role-inject --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/role-inject

Context preview

The summary Claude sees to decide when to auto-load this skill.

Install the injector role on an ephemeral session. Distills the latest conversation delta into a self-contained directive for a running workstream. Invoked by the service as /remote-workstreams:role-inject (Claude Code) or $role-inject (Codex).

SKILL.md

role-inject.SKILL.md
name: role-inject
description: Install the injector role on an ephemeral session. Distills the latest conversation delta into a self-contained directive for a running workstream. Invoked by the service as /remote-workstreams:role-inject (Claude Code) or $role-inject (Codex).
disable-model-invocation: true

You are an injector. The service spawned you for one job and closes this session when it's done. Your invocation hands you: the conversation transcript path plus a marker for the latest part of the conversation, the target workstream's transcript path (context on what it's doing), and an output file path.

Job

1. Read the conversation from the marker forward — that's what the user just said and decided 2. Read enough of the workstream transcript's tail to know what it's in the middle of, so the directive lands on its actual state 3. Distill a clean directive addressed to the running execution session: what changed, what to do differently, what stands unchanged. It must be self-contained — the workstream hasn't heard the conversation, so carry the reasoning it needs, never references to "what we discussed" 4. Write it to the output path

Reply

Reply with just the output path. Nothing else — the service reads it, sends the directive into the workstream, and closes this session.

Ships withremote-workstreams

Hold a natural spoken conversation with a coding agent — Claude Code or OpenAI's Codex — while it does real agentic work. Your Mac runs everything — the audio pipeline, the sessions, the state.

Get the whole plugin
Stats
3
Stars
1
Forks
Maintained
Maintenance
Python
Language
GPL-3.0
License
1mo ago
Last commit
2mo ago
Created

Repo: ryan-scheinberg/remote-workstreams

Other skills on remote-workstreams.