Skip to content
Back to skills

Advise

ASecurity

Ask Claude Code a read-only question from Codex through the sandbox-external bridge.

  • 28 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 2, 2026
ai-agentssecurity

Works with

  • claude code

Security analysis

A100/100

Scanned October 1, 2026

npx -y skills add Borda/AI-Rig --skill advise --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Advise?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Advise
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/borda-advise-ai-rig/badge)](https://www.skillsdirectory.com/skills/borda-advise-ai-rig)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: advise
description: Ask Claude Code a read-only question from Codex through the sandbox-external bridge.
---

> Before asking, read [User Questions](../../rules/codex-user-questions.md).

# Ask Claude Code for Advice

Before dispatch, read `bridge_status`. Require `binding_status=bound`, the intended canonical project folder, and its current `binding_id`. If unbound or wrong project, call `bridge_bind_workspace` with empty arguments; the user types an absolute folder and separately confirms the displayed canonical target in native forms. Retain the returned `binding_id` for this call; never provide a workspace path or scope token from model text. Rebinding invalidates every older ID, even for the same folder. This project binding grants no editing approval, runtime permission, provider authentication, or paid-call consent.

Call `bridge_advise` with required `task` and current `binding_id`; preserve caller-supplied `model`, `effort`, `timeout_seconds`, `depth`, and `run_id`. If effort absent, select and pass it: `low` for narrow mechanical or settled factual work; `medium` for bounded implementation, diagnosis, or review; `high` for cross-file, adversarial, architectural, or security judgment; `xhigh` for unusually broad consequential work; `max` only on explicit request. Never replace supplied effort.

Return compact envelope; retain workspace-relative `transcript_path` and `incident` references, but never copy transcript-only peer `details`. Follow up with fresh call, never session resumption.

If `status=blocked`, open the JSON file referenced by `incident`; inspect its `fault`. For `output-limit`, report incomplete advice. Split by file, symbol, or independent question; use fresh read-only calls with bounded tool output. Reconcile every scope; name unanswered work. Never treat transcript fragments as answers.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.