Agent skill

Shipping And Archiving

A skill your agent uses when the user says "done", "ship it", "finish", "complete", "archive", or otherwise indicates the current design is ready to be shipped.

MITAuto-check passedFrontend & Design

Install Shipping And Archiving

skills CLI

$ npx skills add noemuch/bridge --skill shipping-and-archiving -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install noemuch/bridge shipping-and-archiving --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/noemuch/bridge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/shipping-and-archiving .claude/skills/shipping-and-archiving && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "shipping-and-archiving" agent skill from https://github.com/noemuch/bridge/tree/main/skills/shipping-and-archiving into .claude/skills/shipping-and-archiving/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-and-archiving", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/noemuch/bridge/tree/main/skills/shipping-and-archiving

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add noemuch/bridge --skill shipping-and-archiving -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install noemuch/bridge shipping-and-archiving --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/noemuch/bridge.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/shipping-and-archiving .agents/skills/shipping-and-archiving && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "shipping-and-archiving" agent skill from https://github.com/noemuch/bridge/tree/main/skills/shipping-and-archiving into .agents/skills/shipping-and-archiving/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-and-archiving", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add noemuch/bridge --skill shipping-and-archiving -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install noemuch/bridge shipping-and-archiving --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/noemuch/bridge.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/shipping-and-archiving .cursor/skills/shipping-and-archiving && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "shipping-and-archiving" agent skill from https://github.com/noemuch/bridge/tree/main/skills/shipping-and-archiving into .cursor/skills/shipping-and-archiving/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-and-archiving", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/noemuch/bridge.git --path skills/shipping-and-archiving

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add noemuch/bridge --skill shipping-and-archiving -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install noemuch/bridge shipping-and-archiving --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/noemuch/bridge.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/shipping-and-archiving .gemini/skills/shipping-and-archiving && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "shipping-and-archiving" agent skill from https://github.com/noemuch/bridge/tree/main/skills/shipping-and-archiving into .gemini/skills/shipping-and-archiving/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-and-archiving", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install noemuch/bridge shipping-and-archiving

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add noemuch/bridge --skill shipping-and-archiving -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/noemuch/bridge.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/shipping-and-archiving .github/skills/shipping-and-archiving && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "shipping-and-archiving" agent skill from https://github.com/noemuch/bridge/tree/main/skills/shipping-and-archiving into .github/skills/shipping-and-archiving/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-and-archiving", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add noemuch/bridge --skill shipping-and-archiving -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install noemuch/bridge shipping-and-archiving --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/noemuch/bridge.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/shipping-and-archiving .opencode/skills/shipping-and-archiving && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "shipping-and-archiving" agent skill from https://github.com/noemuch/bridge/tree/main/skills/shipping-and-archiving into .opencode/skills/shipping-and-archiving/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shipping-and-archiving", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: shipping-and-archiving
GitHub stars: 156
Token cost: ~1.7k tokens
SKILL.md length: 542 words
Files: 1
Skills in repo: 5
Repo updated: Jun 3, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when the user says "done", "ship it", "finish", "complete", "archive", or otherwise indicates the current design is ready to be shipped.

Works in 9 steps: Auto-detect pending corrections → Final check → Recipe extraction check → …
The user says done
SKILL.md covers Overview, When to Use, Procedure and Output, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Shipping And Archiving is an agent skill from noemuch/bridge. Use when the user says "done", "ship it", "finish", "complete", "archive", or otherwise indicates the current design is ready to be shipped. Runs final verification (Gate B), archives the CSpec, updates history, extracts a recipe when eligible, and cleans up temp files.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design. It works with Figma. The repository describes itself as: Design in Figma with Claude Code. Bridge connects your terminal to the Figma Plugin API via WebSocket. The licence is MIT.

When your agent uses it

The user says done
Otherwise indicates the current design is ready to be shipped

Example prompts

“ship it”
“finish”
“complete”
“/shipping-and-archiving”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

Auto-detect pending corrections
Final check
Recipe extraction check
Update recipe confidence (if recipe was used)
Archive
Update history log
Persist learnings summary
Brief retro
Cleanup

What it can do on your machine

Read from SKILL.md and the folder at commit 414977f. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and dot).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Shipping And Archiving loads about 1.7k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 542 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~73
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from noemuch/bridge at commit 414977f, republished under its MIT licence (© noemuch). 542 words, ~1,738 tokens.

Download SKILL.mdSave it as .claude/skills/shipping-and-archiving/SKILL.md (or your agent's skills folder).

name: shipping-and-archiving
description: Use when the user says "done", "ship it", "finish", "complete", "archive", or otherwise indicates the current design is ready to be shipped. Runs final verification (Gate B), archives the CSpec, updates history, extracts a recipe when eligible, and cleans up temp files.

Shipping And Archiving

Overview

Formal completion of a design session. Verifies visual correctness one last time (Gate B), moves the CSpec to specs/shipped/, appends a history entry, and — when the design qualifies — extracts a reusable recipe back into the knowledge base.

When to Use

Invoke when the user:

says "done", "ship it", "ship", "finish", "complete", "archive"
has an active CSpec with a snapshot

Do NOT use if:

the user is still iterating — use generating-figma-design or learning-from-corrections
the user is abandoning the work — route to drop (handled by using-bridge command map)

Procedure

1. Auto-detect pending corrections

Check if the snapshot has been updated since the last fix run, or if fix was never run:

If snapshot exists (specs/active/{name}-snapshot.json) AND no learnings reference this spec in learnings.json:
- Re-extract current Figma state (same extraction as the learning-from-corrections skill, step 2)
- Compare against snapshot
- If changes detected:
```
Changes detected since last generation/fix.
Running auto-fix to capture corrections before archiving...
```
  -> Execute the full fix flow via the learning-from-corrections skill (steps 2-10 of its procedure)
- If no changes: proceed
If no snapshot exists: skip (design was never generated, spec-only work)

2. Final check

CSpec exists in specs/active/
User has validated the design (explicit confirmation)
If Figma design exists: matches CSpec intent

3. Recipe extraction check

Evaluate if this design qualifies for recipe extraction:

Eligibility criteria (ALL must be met):

The CSpec is in screen mode (meta.type: screen)
The design was generated and executed in Figma (snapshot exists)
Total corrections during the fix cycle <= 2

If eligible:

This design qualifies for recipe extraction.
Creating recipe: {archetype} (from {name})

Extract recipe:

Take the final scene graph JSON (post-corrections)
Templatize: replace concrete text content with {{ param }} placeholders
Replace component keys with @lookup:ComponentName references
Define parameters based on variable content (title, items, section count, etc.)
Set initial confidence: 0.70 + (0.05 * 1) = 0.75 (first success)
Write to recipes/r-{archetype}-{nnn}.json
Update recipes/_index.json with the new recipe metadata

If not eligible:

Recipe extraction skipped: {reason}
  (screen mode: {yes/no}, corrections: {n}, threshold: <= 2)

Show full SKILL.md (244 more words)Show less

4. Update recipe confidence (if recipe was used)

If a recipe was used during make (check snapshot.meta.recipe):

Increment successCount

Recalculate confidence:

base_score = min(1.0, 0.70 + (successCount * 0.05))
recency_weight = max(0.50, 1.0 - (days_since_last_use * 0.005))
correction_decay = max(0.60, 1.0 - (avgCorrections * 0.15))
confidence = base_score * recency_weight * correction_decay

Update the recipe file and _index.json

5. Archive

bash

mv specs/active/{name}.cspec.yaml specs/shipped/{name}.cspec.yaml

If a snapshot exists:

bash

mv specs/active/{name}-snapshot.json specs/shipped/{name}-snapshot.json

6. Update history log

Append to specs/history.log:

{date} | {name} | {component|screen} | {figma_url} | {learnings_count} | {recipe_extracted: yes/no}

7. Persist learnings summary

Report learnings from this cycle:

Learnings persisted: {n} learnings, {n} flags from this design.
{n} recipe(s) updated, {n} recipe(s) created.

8. Brief retro

What went well? (patterns to repeat)
What was friction? (improvements for the workflow)
What was learned? (reusable knowledge captured in learnings.json)

9. Cleanup

Delete temp files: /tmp/bridge-scene-{name}.json (if exists)
Confirm no stale files remain in specs/active/

Output

## Done: {name}

Figma: {url}
CSpec archived: specs/shipped/{name}.cspec.yaml
Learnings: {n} persisted
Recipe: {extracted as r-{archetype}-{nnn} | updated {recipe} confidence to {score} | none}

Ready for the next design!

<HARD-GATE>
NEVER archive a spec without Gate B evidence from the current or
previous turn (fresh screenshot + explicit user confirmation).

NEVER claim "shipped" without the history.log entry being written. </HARD-GATE>

Red Flags

See the full catalog at references/red-flags-catalog.md (repo-root).

Top flags for this skill:

"User said 'nice', I'll mark it done" → Confirmation must be explicit (done, ship it).
"I'll skip the recipe extraction, it's a one-off" → Eligibility is deterministic (screen + ≤2 corrections). Let the check run.

Verification

This skill is gated by references/verification-gates.md (repo-root):

Gate B — mandatory. Fresh screenshot this turn OR in the immediately preceding turn + explicit confirmation text.

Evidence to surface: screenshot tool result, confirmation text, archive path, recipe extraction decision.

Hooks into other skills

(No cross-skill invocations in v6. The docs cascade was removed.)

The done gate sequence (decision diagram)

dot

digraph done_gate {
  "User says 'done'" [shape=doublecircle];
  "CSpec in specs/active/?" [shape=diamond];
  "Abort: nothing active" [shape=box style=filled fillcolor=lightcoral];
  "Final compile (Gate B)" [shape=box];
  "Compile exit 0?" [shape=diamond];
  "Take final screenshot" [shape=box];
  "Visual matches intent?" [shape=diamond];
  "Iterate via fix" [shape=box];
  "Move CSpec to shipped/" [shape=box];
  "Recipe eligible?" [shape=diamond];
  "Extract recipe to KB" [shape=box];
  "Append history" [shape=box];
  "Done" [shape=doublecircle style=filled fillcolor=lightgreen];

  "User says 'done'" -> "CSpec in specs/active/?";
  "CSpec in specs/active/?" -> "Abort: nothing active" [label="no"];
  "CSpec in specs/active/?" -> "Final compile (Gate B)" [label="yes"];
  "Final compile (Gate B)" -> "Compile exit 0?";
  "Compile exit 0?" -> "Iterate via fix" [label="no"];
  "Compile exit 0?" -> "Take final screenshot" [label="yes"];
  "Take final screenshot" -> "Visual matches intent?";
  "Visual matches intent?" -> "Iterate via fix" [label="no"];
  "Visual matches intent?" -> "Move CSpec to shipped/" [label="yes"];
  "Move CSpec to shipped/" -> "Recipe eligible?";
  "Recipe eligible?" -> "Extract recipe to KB" [label="yes"];
  "Recipe eligible?" -> "Append history" [label="no"];
  "Extract recipe to KB" -> "Append history";
  "Append history" -> "Done";
}

Files

Just SKILL.md in skills/shipping-and-archiving of noemuch/bridge.

Open the folder on GitHubat commit 414977f

Compare with similar skills

Shipping And Archiving next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Shipping And Archiving compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Shipping And Archiving this skillnoemuch/bridge	156	—	~1.7k	Automated safety check: Pass	MIT	4 mo ago
Figma Design System Builderwarpdotdev/warp	65k	2 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
Figma use_figma Plugin API Ruleswarpdotdev/warp	65k	4 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
Figma Design to Codewarpdotdev/warp	65k	4 repos	~2.9k	Automated safety check: Pass	AGPL-3.0	today
Figma Design System Rules Generatorwarpdotdev/warp	65k	3 repos	~4.6k	Automated safety check: Pass	AGPL-3.0	today
Figma Code Connect Componentswarpdotdev/warp	65k	2 repos	~4.2k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
65k GitHub starsUsed in 2 repos~4.4k tokens
Frontend & DesignAuto-check passed
Figma use_figma Plugin API Rules
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
65k GitHub starsUsed in 4 repos~4.4k tokens
Frontend & DesignAuto-check passed
Figma Design to Code
warpdotdev/warp
Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.
65k GitHub starsUsed in 4 repos~2.9k tokens
Frontend & DesignAuto-check passed
Figma Design System Rules Generator
warpdotdev/warp
Creates project-specific design system rules from your codebase so coding agents implement Figma designs with your components, naming and tokens.
65k GitHub starsUsed in 3 repos~4.6k tokens
Frontend & DesignAuto-check passed
Figma Code Connect Components
warpdotdev/warp
Maps published Figma components to their code implementations with Code Connect, using the Figma MCP suggestion and mapping tools.
65k GitHub starsUsed in 2 repos~4.2k tokens
Frontend & DesignAuto-check passed
Cc Design
ZeroZ-lab/cc-design
High-fidelity HTML design and prototype creation. An agent skill from ZeroZ-lab/cc-design.
827 GitHub stars~2.2k tokensUpdated 3 mo ago
Frontend & DesignAuto-check: notes

More from noemuch/bridge

Generating Figma Design
noemuch/bridge
A skill your agent uses when the user requests to design, create, build, generate, or make a new Figma component or screen — including phrases like "make a button", "design a settings page", "build…
156 GitHub stars~4.6k tokensUpdated 4 mo ago
Auto-check passed
Extracting Design System
noemuch/bridge
A skill your agent uses when the user says "setup", "setup bridge", "extract", "extract DS", "onboard", "build knowledge base", "initialize bridge", or is starting Bridge in a project for the first…
156 GitHub stars~1.8k tokensUpdated 4 mo ago
Auto-check passed
Learning From Corrections
noemuch/bridge
A skill your agent uses when the user says they adjusted the design in Figma, mentions "fix", "correct", "learn from", "I changed", "diff", "what changed", or wants the system to incorporate manual…
156 GitHub stars~2.4k tokensUpdated 4 mo ago
Auto-check passed
Using Bridge
noemuch/bridge
A skill your agent uses when any Bridge command is invoked (make, fix, done, setup, drop, status) or any Figma / design-system / compiler / Bridge workflow topic is raised.
156 GitHub stars~1.4k tokensUpdated 4 mo ago
Auto-check passed

Works with

Figma

Questions about Shipping And Archiving

What does Shipping And Archiving do?

A skill your agent uses when the user says "done", "ship it", "finish", "complete", "archive", or otherwise indicates the current design is ready to be shipped. Shipping And Archiving is an agent skill from noemuch/bridge. Use when the user says "done", "ship it", "finish", "complete", "archive", or otherwise indicates the current design is ready to be shipped.

When should I use Shipping And Archiving?

Shipping And Archiving fits situations like: the user says done; otherwise indicates the current design is ready to be shipped.

How do I install Shipping And Archiving in Claude Code?

Run `npx skills add noemuch/bridge --skill shipping-and-archiving -a claude-code`. Or copy the skill folder (skills/shipping-and-archiving in noemuch/bridge) into .claude/skills/shipping-and-archiving in your project. Claude Code loads it when a task matches its description.

How do I install Shipping And Archiving in Codex?

Run `npx skills add noemuch/bridge --skill shipping-and-archiving -a codex`. Or copy the skill folder (skills/shipping-and-archiving in noemuch/bridge) into .agents/skills/shipping-and-archiving in your project. Codex loads it when a task matches its description.

Can I use Shipping And Archiving in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add noemuch/bridge --skill shipping-and-archiving -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/shipping-and-archiving, .gemini/skills/shipping-and-archiving, .github/skills/shipping-and-archiving and .opencode/skills/shipping-and-archiving in your project.

What does Shipping And Archiving need to run?

SKILL.md names no scripts, command-line tools or credentials: Shipping And Archiving is instructions for the agent only.

Does Shipping And Archiving access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Shipping And Archiving safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Shipping And Archiving use?

Shipping And Archiving is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Shipping And Archiving use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Shipping And Archiving?

Skills that share tags, products or a category with Shipping And Archiving: Figma Design System Builder (warpdotdev/warp, 65k stars), Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars), Figma Design to Code (warpdotdev/warp, 65k stars) and Figma Design System Rules Generator (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Shipping And Archiving?

noemuch (a GitHub user) maintains it in noemuch/bridge, which has 156 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on June 3, 2026.

Source: noemuch/bridge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Shipping And Archiving

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Shipping And Archiving

Overview

When to Use

Procedure

1. Auto-detect pending corrections

2. Final check

3. Recipe extraction check

4. Update recipe confidence (if recipe was used)

5. Archive

6. Update history log

7. Persist learnings summary

8. Brief retro

9. Cleanup

Output

Red Flags

Verification

Hooks into other skills

The done gate sequence (decision diagram)

Files

Compare with similar skills

Similar skills

More from noemuch/bridge

Related

Questions about Shipping And Archiving