القائمة
Deterministic read-only Paperclip issue, document, and approval-link verification with strict JSON output.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Build deterministic, complete 30-day issue-level evidence and rank recurring operating-system improvements for the CEO routine.
Decide when CEO self-improvement should stay in additive runtime guidance versus becoming a PR against the Micronaut Agent Company source repository.
"Reference the upstream GitHub gh CLI skill only for explicit human/operator exceptions where a non-plugin GitHub client is authorized. Normal GitHub API operations must use the GitHub Sync plugin tools, including the Hermes MCP-bridged runtime names when present. Do not depend on a propagated GITHUB_TOKEN and do not search the filesystem, plugin config, or other files for a token. Any maintainer-visible non-plugin GitHub write still requires the manual GitHub-flavored Markdown footer: one blank line, `---` on its own line, then `###### \u2728 This message was AI-generated using <exact model id>`."
Search-only Skills marketplace discovery for CEO Training; inspect candidates and prepare evidence-backed approval requests without installing, updating, assigning, or executing any skill.
Shared GitHub, GitHub Sync plugin, footer, PR-linking, and review-thread protocol used by Micronaut company agents.
Diagnose, plan, implement, verify, and review Micronaut-specific GraalVM native-image work across Native Build Tools, reachability metadata, micronaut-graal, micronaut-build GraalVM support, generated AOT/native assets, and CI reports.
| name | paperclip-control-plane |
| description | Deterministic read-only Paperclip issue, document, and approval-link verification with strict JSON output. |
Use the bundled CLI before interpreting repeated REST steps:
node <skill-directory>/scripts/paperclip-workflow.mjs snapshot --issue "$PAPERCLIP_ISSUE_ID" --document qa-intake
node <skill-directory>/scripts/paperclip-workflow.mjs verify --issue "$PAPERCLIP_ISSUE_ID" --participant "$PAPERCLIP_AGENT_ID"
Commands:
snapshot: fetch issue, heartbeat context, and selected durable documents as normalized JSON.verify: assert expected status, assignee, active participant, stage outcome, and document presence.approval-link: verify that an approval is linked to the current issue.All calls require PAPERCLIP_API_URL and PAPERCLIP_API_KEY. The URL must be an origin with no credentials, path, query, or fragment; plaintext HTTP is accepted only on loopback. Options are command-specific, singleton options reject duplicates, and unknown options fail before any request. Treat exit code 2 as a failed state assertion, not permission to improvise a write.
Do not attempt a cross-agent heartbeat invocation. Agent-authenticated callers may invoke only themselves; correct execution-policy routing or assignment must wake the next participant. If routing is correct but no run is queued, record a runtime wake blocker.
This skill grants no document mutation, GitHub, repository, implementation, closure, or publication authority. Permitted document writes and stage decisions remain on native Paperclip tools because v2026.626 exposes no atomic client precondition that can safely fence keyed-document replacement or same-agent stage re-entry. If a native document operation cannot guarantee the requested key, stop instead of retrying a remapped write.
See references/instruction-automation-audit.md for automated and deferred candidates.