Skip to content
Back to skills

Autopilot Ship

ASecurity

Use when preparing deployment/release or a delivery archive (package mode). Owns release; default preset. Not for code, new inference/evaluation, report rewriting, or unauthorized deployment; package mode does not run the deployment/review loop.

  • 8 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 3, 2026
ai-agentsnode

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned October 5, 2026

npx -y skills add dmlguq456/hearting --skill autopilot-ship --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Autopilot Ship?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Autopilot Ship
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dmlguq456-autopilot-ship/badge)](https://www.skillsdirectory.com/skills/dmlguq456-autopilot-ship)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
# GENERATED METADATA — edit harness-manifest.json, then run tools/generate.py.
name: autopilot-ship
description: "Use when preparing deployment/release or a delivery archive (package mode). Owns release; default preset. Not for code, new inference/evaluation, report rewriting, or unauthorized deployment; package mode does not run the deployment/review loop."
argument-hint: "<task description (optional)> [--mode default|package] [--intensity direct|quick|standard|strong|thorough|adversarial]"
metadata:
  group: entry
  fam: app
  invocation_class: entry-router
  modes: ["default", "package"]
  blurb: "Prepare deployment/release setup or package existing artifacts."
  use_when: "Use when preparing deployment/release or a delivery archive (package mode). Owns release; default preset."
  not_for: "Not for code, new inference/evaluation, report rewriting, or unauthorized deployment; package mode does not run the deployment/review loop."
---

# autopilot-ship

This is a compact pre-approval entry router. Its manifest-owned frontmatter is
the authoritative discovery metadata; it intentionally contains no execution
procedure.

## Pre-approval boundary

Use only this router, `harness-manifest.json`, and `core/WORKFLOW.md §0.2` to
propose a route. Present the one-time confirmation in `core/WORKFLOW.md §0.4`
unless the same route and scope are already approved. Do not load references
before approval.

## Post-approval owner contract

After approval, direct/quick sessions and the `standard+` dispatch-depth-1 owner load
`capabilities/autopilot-ship.md`, then use the Reference Index below. Assigned
stage workers load only their assigned stage contracts.

## Reference Index

| File | Load when | Obligation |
|---|---|---|
| [`references/owner-execution.md`](references/owner-execution.md) | After approval, by the selected direct/quick session or dispatch-depth-1 owner | Read the complete execution procedure before material work. This is the router's only post-approval reference edge. |

## Guard pointer

Follow the portable artifact, worktree, role, and verification guards in the
selected owner contract. Before the first durable capability artifact, compile
and bind the checked route even for direct intensity; direct is a compiled
inline node, not route absence. A restriction on native subagents/agents is
surface-local and never selects direct execution. Runtime projections must
report unsupported mechanics and must not claim physical instruction masking,
token, billing, or cost savings without verified evidence.

Files in this skill

  • SKILL.md2.4 KB
  • references/examples.md1 KB
  • references/owner-execution.md8.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.