跳到正文
cccskills
免费在 GitHub 公开

ask

Send a request to a CCB agent with `ask`.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(3)

  • SKILL.md4.4 KB
  • RUNTIME.md4.3 KB
  • SKILL.md.powershell4.5 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Use this when the user asks you to delegate with CCB, or when project memory says to use CCB ask for collaboration.

Decision Card

Before every ask, decide:

  1. Need delegation? If no, answer directly.
  2. Dependency gate:
    • Default: do not use --chain.
    • Use --chain only when the current active CCB task cannot finish until this exact child result arrives. Then stop for continuation.
    • Communication tests, batch sends, notifications, and independent work do not become chain dependencies merely because replies are requested.
  3. Result intent:
    • --silence: publish/execute task; success result not needed. Failures, blockers, risks, or required next actions still surface.
    • --compact: result wanted, but only distilled findings/status/risks/blockers/next actions.
    • + --artifact-reply: consultation/analysis/report where full text should be preserved.
    • plain ask: short question or short handoff where inline text is enough.
  4. Request fidelity:
    • + --artifact-request: exact transient input (logs/output/diffs/copied contents/config/JSON/YAML/table/structured text). Prefer repo paths when the target can read files directly.
    • --artifact-io: request and reply both need artifacts.

Guardrails

  • Do not probe --chain; if unsure there is an active parent job, use plain ask.
  • If CCB says ask --chain requires an active parent job, retry once with plain ask for user-requested delegation.
  • Never add --chain merely to make a rejected plain ask succeed. If the work is independent and no success result is needed, use --silence; otherwise report the routing limitation instead of inventing a dependency.
  • --chain and --silence usually conflict; avoid mixing unless explicit.
  • Avoid --silence --artifact-reply; silence means no caller result needed; artifact-reply preserves one.
  • Artifact flags are orthogonal to --chain, --silence, and --compact. They preserve content, not dependency shape.
  • Automatic spill for text over 4 KiB is a fallback, not the primary rule.
  • --artifact-* modes are CCB/daemon managed; targets do not write artifact reply files.
  • Plain nested ask from an active CCB task is rejected. Use --chain only for a real child dependency; use --silence for independent no-result work.
  • In A --silence -> B, B still runs an active job. B-to-C depends on whether B needs C's result.
  • In task chains, each needed-result hop uses --chain; CCB then propagates continuations.
  • Finish an inbound CCB task in its current turn.
  • If the original caller is a registered CCB agent, CCB routes that turn's terminal result through the existing lineage; do not open a new ask to report completion to the original caller.
  • Direct CLI submitters read terminal results from control output such as watch or trace.
  • If the current task is a CCB result-chain continuation, answer the current task directly with the final result. Do not use ask, --chain, or --silence to send that final result to the original caller; CCB routes the continuation completion upstream.
  • --silence is not an active-job correction channel. Use ccb followup <active_job_id> --message "<correction>" only when the target provider supports exact active-turn injection; only injected is success. On rejected, too_late, or terminal, cancel and resubmit the complete corrected task instead of queueing a correction as ordinary work.
  • A completed CCB job means provider execution ended normally; it does not by itself prove business acceptance.
  • ask get, pend, watch, and ping are diagnostics-only commands for explicit debugging requests, not normal ask workflow tools.
  • Do not manually append output-policy text; stable reply policy comes from managed CCB memory, and ask adds only requested compact/silent mode metadata.

Always send MESSAGE through the <<'EOF' ... EOF heredoc below. No other form is allowed. Use no flags or insert selected flags before "$TARGET":

command ask "$TARGET" <<'EOF'
$MESSAGE
EOF
command ask --chain --artifact-reply "$TARGET" <<'EOF'
$MESSAGE
EOF

After the command returns, end the turn. Do not wait for a reply, do not run ask get / pend / ping / watch, do not poll. For --chain, report only that delegation was submitted.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

ask

免费

Send a request to another CCB agent with `ask`.

中文简介正在准备中。当前显示原文说明。

SeemSeam/claude_codex_bridge35782026年10月14日 更新

ask

免费

Delegate work or request information from another CCB-managed agent using ask. Use when the user asks Grok to ask, delegate to, hand off to, consult, or send work to a named CCB agent, or when project memory requires CCB collaboration.

中文简介正在准备中。当前显示原文说明。

SeemSeam/claude_codex_bridge35782026年10月14日 更新

Submit one node result to the assigned Reviewer and finish only after a bounded pass/rework chain.

中文简介正在准备中。当前显示原文说明。

SeemSeam/claude_codex_bridge35782026年10月14日 更新

Execute one scoped implementation or investigation item and return evidence without changing workflow authority.

中文简介正在准备中。当前显示原文说明。

SeemSeam/claude_codex_bridge35782026年10月14日 更新

Execute one bounded CCB work item and report evidence without changing workflow authority.

中文简介正在准备中。当前显示原文说明。

SeemSeam/claude_codex_bridge35782026年10月14日 更新

ccb-clear

免费

Clear CCB managed agent conversation context with `ccb clear`. Use for `/ccb-clear`, `$ccb-clear`, `$ccb_clear`, or requests to reset one or more CCB agent contexts without deleting project state.

中文简介正在准备中。当前显示原文说明。

SeemSeam/claude_codex_bridge35782026年10月14日 更新

查看 SeemSeam 的全部技能

报告此技能的问题