speed-line-delivery
Deliver terminal instructions with shell-labeled lanes and one-line command blocks so users can execute quickly without context confusion. Use when users are working across multiple terminals, mixing chat and shell actions, hitting PowerShell parsing errors, or asking to learn while still completing setup/ops tasks fast.
Best use case
speed-line-delivery is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Deliver terminal instructions with shell-labeled lanes and one-line command blocks so users can execute quickly without context confusion. Use when users are working across multiple terminals, mixing chat and shell actions, hitting PowerShell parsing errors, or asking to learn while still completing setup/ops tasks fast.
Teams using speed-line-delivery should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/speed-line-delivery/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How speed-line-delivery Compares
| Feature / Agent | speed-line-delivery | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Deliver terminal instructions with shell-labeled lanes and one-line command blocks so users can execute quickly without context confusion. Use when users are working across multiple terminals, mixing chat and shell actions, hitting PowerShell parsing errors, or asking to learn while still completing setup/ops tasks fast.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Speed Line Delivery ## Overview Run command coaching with minimal ambiguity. Label every command with an execution lane and provide one copy-paste line at a time. ## Workflow ### Step 1: Declare lanes first Declare active lanes before giving commands: 1. `[CHAT]` for setup/config/git. 2. `[SERVER]` for long-running services. 3. `[OPS]` for API calls/tests. If only one terminal is used, map all commands to `[CHAT]`. ### Step 2: Use speed-line command format For each step, output exactly: 1. Objective: one short sentence. 2. Lane: one of `[CHAT]`, `[SERVER]`, `[OPS]`. 3. Command: one line only in a fenced code block. 4. Success signal: one line describing expected output. Never split command flags onto a second line unless explicitly teaching multiline syntax. ### Step 3: Enforce one-line copy/paste discipline Use these rules: 1. Put full command on one line. 2. Quote paths with spaces. 3. Use `$repo = "C:\\path"` once, then reuse variable. 4. Avoid trailing prose on command lines. 5. Do not prepend command with conversational text. ### Step 4: Recover from parse/context errors fast If user gets parse errors or wrong working directory: 1. Re-anchor directory first: `cd <repo>`. 2. Reissue the same command as a single line. 3. If command was line-wrapped, replace with variable form. 4. Ask for exact terminal output after each command before giving next. ### Step 5: Keep learning active while shipping When user asks to learn and move quickly: 1. Give command first. 2. Add one-line explanation after success signal. 3. Move to next command immediately. ### Step 6: Use standard response template Use this template: ```text Objective: <what this step does> Lane: [CHAT|SERVER|OPS] Command: <single-line command> Success signal: <what user should see> ``` ## References 1. Quick command patterns: `references/command-patterns.md`
Related Skills
kindle-app-delivery
Build, sideload, and publish the SCBE Kindle/Fire app using Capacitor, Gradle, ADB, and Amazon Appstore checklist steps.
scbe-training-pipeline
Manage the SCBE SFT training data pipeline — merge sources, validate quality, track corpus statistics, generate new SFT pairs from codebase, trigger training runs, and push to HuggingFace. Use when working with training data, SFT generation, data quality, or model fine-tuning.
scbe-training-pair-authoring
Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.
scbe-spin-conversation-engine
Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.
scbe-research-training-bridge
Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.
scbe-document-management
Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.
scbe-colab-bridge
Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.
scbe-claim-to-code-evidence
Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.
scbe-autonomous-worker-productizer
Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.
multi-agent-cloud-offload
Deterministically sort, bundle, verify, and offshore local files through multiple AI/model lanes while capturing training rows and method evidence. Use when Codex needs to inventory folders, batch-process files, upload them to cloud targets such as rclone-backed Google Drive, Hugging Face, or GitHub, and only delete sources after the configured number of verified targets succeed.
long-form-work-orchestrator
Run long-form engineering work in checkpointed phases with deterministic artifacts, resilience handling, and end-of-run reliability reporting.
scbe-code-scanning-ops
Operate GitHub code scanning and CodeQL remediation for SCBE repositories. Use when triaging code-scanning alerts, mapping alert classes to fix patterns, validating targeted regressions, or wiring dedicated CodeQL workflows and runbooks into the repo.