القائمة
Cut an emisar product release end to end — changelog, version, license date, gate, commit, signed tag, push, and GitHub release. Use when the user asks to cut or publish a product release.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Author, validate, test, distribute, and certify a custom Emisar action pack for a customer fleet. Use when wrapping internal CLIs or services as declared actions, writing or reviewing pack/action YAML, testing a pack locally, rolling a pack out to runners, hosting a private pack registry with packctl, publishing a new pack version, retiring an unsafe version, or diagnosing pack trust and hash-mismatch issues.
Connect an LLM or MCP client to Emisar and certify the connection end to end. Use for installing the emisar-mcp stdio bridge, registering a local client (Claude Code, Cursor, Zed, Copilot CLI, and other stdio clients), wiring a cloud connector (Claude.ai, ChatGPT), repairing a broken client registration, or proving that discovery, action execution, and audit work through the configured client. For installing the on-host runner itself, use the install-emisar skill.
Install, configure, repair, and certify the Emisar runner on a host end to end for customer onboarding. Use for first-run setup, runner installation, guided pack discovery and selection, host capability coverage, custom-pack recommendations, pack credentials, upgrades, supervised-service migration, authenticated MCP dispatch, or any request to diagnose and report runner health across the host, control plane, registry, action execution, and audit trail. After runner setup, reuse the current authenticated Emisar MCP connection or offer to connect the operator's agent through connect-llm; when a required host job has no suitable pack, offer the public author-pack workflow.
Investigate, contain, and permanently remediate production incidents through Emisar. Use when an operator asks an agent to investigate production, explain why a service is degraded, stop the bleed, stabilize an environment, or fix an infrastructure incident; gather evidence, test hypotheses, use the smallest authorized action, fall back to explicitly approved break-glass access only when Emisar has no viable path, turn the root cause into a source-controlled application or infrastructure-as-code fix, verify the operator's deployment, iterate until recovery, and write the incident report. An investigation-only request authorizes observation, never a production-changing or break-glass action.
Write and edit clear, distinctive, human-quality content for emisar across marketing pages, product UI, documentation, blog posts, announcements, SEO pages, CTAs, and positioning. Use when copy sounds corporate, generated, vague, overcomplicated, over-marketed, tonally flat, or inconsistent; when a surface needs a confident, direct, friendly professional voice; or when approved writing samples should become a reusable brand voice.
Drain a project's .agent/tasks/ queue autonomously and run-to-completion, taking EACH task to a ship-ready bar — `coop tasks claim` a 00_todo/ task, build it, gate it green, self-review it against the house rules (portal Iron Laws / runner security posture / pack conventions + the .agent/rules KB) AND every hat (security, UX, marketing, docs, code quality, tests), ITERATE until it's clean, then COMMIT IT ON ITS OWN and `coop tasks done` — without quitting early. A Stop hook scoped to this skill blocks quitting while any task is actionable. Use to "work all the tasks" / drain a backlog to a high bar / run an unattended sweep.
| name | ops-release |
| description | Cut an emisar product release end to end — changelog, version, license date, gate, commit, signed tag, push, and GitHub release. Use when the user asks to cut or publish a product release. |
| effort | medium |
| argument-hint | [vX.Y.Z] [anchor-commit] |
| allowed-tools | Read, Grep, Glob, Bash, Write, Edit |
Read docs/release.md in full and execute that
canonical runbook in order. Cross-read the current changelog entries and use
/content-director for both the plain-text website summary and the Markdown
GitHub release notes.
Do not duplicate or improvise the release procedure here. The invariants are:
portal/VERSION, and anchor describe one window;LICENSE.md carries that release's three-year BUSL Change Date;git push, tag push, and gh release create requires explicit user
confirmation because it leaves the machine.After publication, verify the signed tag, GitHub release, changelog page/feed, and any release workflow triggered by the tag, then record the result in the local portal agent log.