Skip to content
cccskills
FreePublished on GitHub

e

Explain a file, error, design, diff, or concept like a helpful engineering colleague: grounded in evidence, concise, and with useful follow-up threads. Use when the user asks for a clear explanation of the current work or codebase.

The English summary is being prepared. Showing the original description.

btseytlin/ultrapack46 stars(GitHub 46 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md867 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Explain

Use this as the Codex and Pi equivalent of /up:e.

  1. If the user named a file, error, diff, or behavior, inspect it before explaining. If they did not, infer the most recent clear topic and state what you selected; ask once only if no target is clear.
  2. Lead with the mechanism that answers the question. Assume the reader only vaguely remembers surrounding context.
  3. Give evidence in plain language, normally one to four paragraphs. Avoid doc dumps, invented terminology, and unexplained shorthand.
  4. End with up to three deeper follow-up threads only when they would add real value.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Run a bounded implement-attack-repair loop for a user-specified task. Use when work needs repeated independent criticism: perform the task, dispatch a fresh attacker, verify significant findings, repair them, and stop on a clean attack or the user's round limit.

The English summary is being prepared. Showing the original description.

btseytlin/ultrapack46Updated Oct 15, 2026

expand

Free

Turn one user criticism into a principle-level fix: find the violated principle, every similar occurrence, and fix the shared cause. Use only when the user explicitly invokes expand, $expand, /up:expand, or /skill:expand.

The English summary is being prepared. Showing the original description.

btseytlin/ultrapack46Updated Oct 15, 2026

Use when a task needs an isolated checkout. Verify the worktree location, keep mutable environments and build outputs local, and run only authorized setup and checks.

The English summary is being prepared. Showing the original description.

btseytlin/ultrapack46Updated Oct 15, 2026

Contract for hands-off mode — the ultrapack workflow variant that minimizes user prompts after Design, takes the safest reversible path, and logs every auto-choice for one end-of-task review. Referenced by the workflow entry point and child skills (udesign, uplan, uexecute, uverify, ureview). Read when the task file's **Mode:** header is `hands-off`.

The English summary is being prepared. Showing the original description.

btseytlin/ultrapack46Updated Oct 15, 2026

Use when the user explicitly asks to launch and supervise a job. Require an authorized launch, monitoring, recovery, and teardown contract. Detect failures without inventing permission to restart or spend money.

The English summary is being prepared. Showing the original description.

btseytlin/ultrapack46Updated Oct 15, 2026

make

Free

Orchestrate the full Ultrapack workflow in Codex and Pi: create or resume a task file, design, plan, execute, verify, review, and validate the observable goal. Use when the user asks to build, fix, or deliver a non-trivial change with the complete workflow.

The English summary is being prepared. Showing the original description.

btseytlin/ultrapack46Updated Oct 15, 2026

See all skills by btseytlin

Report a problem with this skill