メニュー
Use when the user asks for LinearPlus, Linear initiatives through API, Linear GraphQL initiative creation, attaching Linear projects to initiatives, or when the Linear connector cannot create/list initiatives.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user asks about Eidos, Eidos AGI, platform status, `eidos do`, closeout, cleanup before done, docket-task orchestration, evidence verification, praxis learning, gateway routing, vault/secrets, plugins, or which Eidos AGI specialist system should handle a task. This skill tells Codex to call the installed `eidos` CLI first; MCP and plugins should only point to CLIs, while CLIs provide progressive reveal of the deeper tool graph.
Investigate current context before predicting likely futures, failures, user objections, and concrete changes. Use when Zoltar needs to research an app, plugin, architecture, workflow, plan, decision, or implementation and answer what is likely to go wrong, what evidence supports it, what complaint or failure is being prevented, and what should change today.
Answer a specific foresight decision question with researched evidence, a clear judgment, likely futures, user complaint prediction, and concrete changes. Use when Daniel asks whether an idea, implementation, plugin, architecture, or workflow is likely to be regretted, whether it is the right thing in the right place with the right authority, or what decision should be made given future effects.
Compatibility entrypoint for Zoltar foresight. Use when Daniel mentions Zoltar, asks to predict the future, asks for second-order effects, asks what he will complain about, or wants future-backed product/spec changes; route the work through researched evidence, judgment, structured output, doer/checker handoff, and self-improvement notes rather than generic prediction.
Maintain and check the Eidos marketplace when plugins must work in both Claude Code and Codex. Use when adding, refactoring, auditing, or debugging marketplace plugins, dual-host packaging, .claude-plugin and .codex-plugin manifests, root marketplace entries, source/store/cache drift, install proof, or host-neutral plugin payloads.
Challenge whether a Zoltar prediction, product idea, plugin, workflow, category framing, or architecture is overfit to existing market patterns. Use when Daniel asks for a Challenger Matrix, anti-consensus review, category redefinition, frontier user needs, non-consensus futures, Doubter voice, or whether an answer is too derivative, market-shaped, competitor-shaped, or copied from current agent/product patterns.
| name | use-linearplus |
| description | Use when the user asks for LinearPlus, Linear initiatives through API, Linear GraphQL initiative creation, attaching Linear projects to initiatives, or when the Linear connector cannot create/list initiatives. |
Use the installed LinearPlus CLI when Linear initiative workflows are needed and the connected Linear tool surface does not expose the required operation.
Run the smallest relevant linearplus command first, then report from its JSON
or fail-closed output. Do not use browser UI automation as the primary path.
Useful entrypoints:
linearplus --help
linearplus initiative-get --name "Greenmark AI Search Visibility"
linearplus initiative-ensure --name "Greenmark AI Search Visibility" --status Planned
linearplus attach-project --initiative-id <initiative-id> --project-id <project-id>
linearplus greenmark-bootstrap --dry-run
linearplus greenmark-bootstrap
If the linearplus command is not on PATH, resolve the plugin root from this
skill file and run:
bin/linearplus --help
LINEAR_API_KEY or LINEARPLUS_LINEAR_API_KEY.Use this procedure when LinearPlus needs a Linear API key.
Confirm the task needs live Linear API access. Run the dry-run command first and explain what the live command would change.
Ask Daniel to create or choose a Linear personal API key.
Linear's current docs place personal API keys under:
Settings > Account > Security & Access.
If Daniel is not an admin and cannot create a key, tell him the workspace
may restrict member API keys under:
Settings > Administration > API > Member API keys.
Ask Daniel to provide the key only through an approved local secret path or shell environment. Do not ask him to paste the token into chat.
Verify presence without revealing the value:
test -n "$LINEARPLUS_LINEAR_API_KEY" || test -n "$LINEAR_API_KEY"
Run one read or dry-run-safe check first when possible, then perform the narrow live mutation that Daniel requested.
Capture evidence with the command, redacted output, created or reused Linear ids/urls, and any permission blocker. Never record the token.
Recommended temporary shell form:
export LINEARPLUS_LINEAR_API_KEY="..."
linearplus initiative-get --name "Greenmark AI Search Visibility"
Recommended persistent handling is a local vault or shell profile entry owned by Daniel, not plugin-managed storage.
Official references:
https://linear.app/docs/api-and-webhookshttps://linear.app/developers/graphqlUse linearplus greenmark-bootstrap to create or reuse the
Greenmark AI Search Visibility initiative and attach project
079b8875-9c80-41c8-b4b0-ea09834a7065.
Start with:
linearplus greenmark-bootstrap --dry-run
Then run live only when a valid Linear API key is available in environment or approved vault-backed shell context.