ask
Skill4 starsChanged todayMITView on GitHub
[oh-my-agy] Ask a locally installed external advisor CLI (Claude Code, Gemini CLI, or Codex CLI) for a second opinion, blind-claim --doubt review, or brainstorm, and save a reusable artifact. Use for $ask claude|gemini|codex [--doubt] <question>, or when the user wants another model's opinion.
- Reads credentials
78 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- web3illy/private-second-brain-skillstheir own version, first seen Nov 16, 2026
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- mad01/thismoontheir own version, first seen Nov 15, 2026
- AndyMelnykov/obsidian-claudetheir own version, first seen Nov 15, 2026
- finolabs/vibecodetheir own version, first seen Nov 15, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
Used with
Projects with it also use daily-arxiv, exp-eval and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
skyllwtSkillexp-pilot-eval
Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.
Also in 4 projects that use this
skyllwtSkillexp-pilot-run
Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.
Also in 4 projects that use this
phanghonghaoSkillposter
HTML/CSS A4 海报生成。从沙龙/活动 Markdown 文件生成科技风 A4 海报 PDF/PNG。Use when user mentions: poster, 海报, 海报生成, make poster, generate poster, 活动海报, 沙龙海报.
Also in 4 projects that use this
- +6 more from Lambenthan
- +1 more from skyllwt
Other versions78 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- Yeachan-Heo/oh-my-codex★ 34k15% same
Wrote their own version · 77
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- acunniffe/git-ai★ 3ksame name
- git-ai-project/git-ai★ 3ksame name
- DAIR-AutoResearch/AutoSci★ 1.7ksame name
- PKU-DAIR/AutoSci★ 1.7ksame name
- skyllwt/AutoSci★ 1.7ksame name
- skyllwt/OmegaWiki★ 1.7ksame name
- keli-wen/agy-staff★ 873same name
67 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- rules/AGENTS.mdAGENTS.md
- ai-slop-cleanerSkill
- analyzeSkill
- autopilotSkill
- cancelSkill
- code-reviewSkill
- deep-interviewSkill
- deep-researchSkill
- doctorSkill
- hudSkill
- loftSkill
- modernizeSkill
- performance-goalSkill
- prSkill
- ralplanSkill
- releaseSkill
- skillSkill
- teamSkill
- threat-modelSkill
- ultragoalSkill
- ultraqaSkill
- visual-ralphSkill
- wikiSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 64 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use a locally installed external advisor CLI for focused questions, architecture/code reviews, blind-claim --doubt critiques, …
- Very specific: line 26
If no backend is given, pick the installed one that best fits the request (command -v claude gemini codex).
- Distinctive: line 30
Never interpolate prompts, code excerpts, or unified diffs into CLI command-line arguments.
- Very specific: line 42
Older-CLI flag fallback: if an older installed CLI version rejects --sandbox, --approval-mode, or --permission-mode, inspect <cli> --help …
- Very specific: line 47
When invoked with --doubt ($ask claude|gemini|codex --doubt <target>), run an anti-anchored adversarial critique that strips author …
- Very specific: line 60
Doubt/Review Theater Circuit Breaker: if >= 2 consecutive --doubt or review cycles return prose critiques ("substantive findings") with 0 …
- Distinctive: line 64
After running, save a reusable markdown artifact to:
“Common” is measured: kept by at least 6 in 10 of the 64 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ask (Local Advisor CLI)
Use a locally installed external advisor CLI for focused questions, architecture/code reviews, blind-claim --doubt critiques, brainstorming, or independent second opinions.
Usage
$ask claude <question or task>
$ask gemini <question or task>
$ask codex <question or task>
$ask claude --doubt <target diff, commit range, plan, or file>
$ask gemini --doubt <target diff, commit range, plan, or file>
$ask codex --doubt <target diff, commit range, plan, or file>Backend selection
claudewhen the user asks for Claude/Anthropic.geminiwhen the user asks for Gemini CLI.codexwhen the user asks for Codex/OpenAI.- If no backend is given, pick the installed one that best fits the request (
command -v claude gemini codex). If none is available, explain that a local CLI is required. Do not silently switch to an MCP or remote provider.
Sandboxed 0600 Temp-File stdin Invocation
Never interpolate prompts, code excerpts, or unified diffs into CLI command-line arguments. Untrusted code, backticks, $() expressions, or prompt-injected strings inside diffs must never undergo shell expansion or trigger workspace mutations in an external agent CLI.
- Create an atomic
0600temp file ($tmpfile) and redact secrets: allocate the file atomically viatmpfile=$(mktemp "${TMPDIR:-/tmp}/omagy-ask.XXXXXX")— never use predictable/tmpfilenames (such as PID- or slug-based paths), which risk symlink/pre-creation races. Include all required context inside"$tmpfile"because the external CLI cannot see this conversation, and scrub/redact all PEM private-key blocks (-----BEGIN ... PRIVATE KEY-----), standalone or inline secrets, API keys, tokens (sk-...,sk_live_...,rk_live_...,ghp_...,github_pat_...,glpat-...,xox[baprs]-...,AIza...,npm_...,SG....,AKIA...,ASIA...,pypi-..., JWTs, credentialed database URIs,Bearerheaders,--api-key/--tokenflags, and.envvalues) before writing"$tmpfile". - Pipe
"$tmpfile"overstdininto a read-only sandbox:
codex exec --sandbox read-only -C <dir> - < "$tmpfile"
gemini --approval-mode plan -p "" < "$tmpfile"
claude -p --permission-mode plan --disallowedTools "Bash,Edit,Write,MultiEdit,NotebookEdit" < "$tmpfile"- Claude read-only defense-in-depth & cleanup: in addition to
--permission-mode plan --disallowedTools "Bash,Edit,Write,MultiEdit,NotebookEdit", prepend an explicit read-only instruction at line 1 of"$tmpfile"("READ-ONLY ADVISORY MODE: Do not create, modify, delete, or execute any workspace mutations; analyze the input below and respond with text only.") and always delete"$tmpfile"(rm -f "$tmpfile") immediately after capturing output (including on non-zero exit or timeout). Clean up"$tmpfile"aftercodexandgeminiruns as well. - Older-CLI flag fallback: if an older installed CLI version rejects
--sandbox,--approval-mode, or--permission-mode, inspect<cli> --helpfor its supported read-only/plan flag, keep--disallowedTools "Bash,Edit,Write,MultiEdit,NotebookEdit"onclaudewhenever supported, and preserve< "$tmpfile"stdinredirection — never revert to passing prompt text as a shell-interpolated CLI argument string. - Network & Antigravity sandbox discipline: prepare and remove
"$tmpfile"in standard sandboxed steps (BypassSandbox: false). Try the advisor CLI command in Standard Sandbox Mode first; if it fails due to network isolation, re-run only the advisor CLI invocation withBypassSandbox: true(keepingtoolSummaryidentical) and a boundedWaitMsBeforeAsync, letting long runs finish in the background.
Adversarial Blind-Claim Review (--doubt)
When invoked with --doubt ($ask claude|gemini|codex --doubt <target>), run an anti-anchored adversarial critique that strips author persuasion before consulting the advisor:
- Construct a Redacted Blind-Claim Packet in
"$tmpfile"(tmpfile=$(mktemp "${TMPDIR:-/tmp}/omagy-ask.XXXXXX")):## ARTIFACT: raw unified diff (e.g., generated viash <plugin>/hooks/run.sh review-package <workspace> <base_sha> <head_sha>orgit diff <base>..<head>), touched file slices, or target spec/plan markdown (with any literal secrets, tokens, keys, or.envvalues redacted).## CONTRACT: verbatim acceptance criteria, spec/plan invariants, public signatures, repository callergrepcontext, and active guard rules (omagy_wiki/agreements.mdorCONSTRAINTS.mdwhen present).## RAW COMMAND EVIDENCE: exact verification commands executed, numeric exit codes, and raw failing/passing test or typecheck output (redacting any inline tokens/secrets).- Strict Anti-Anchoring Omission: omit all author
CLAIMsummaries, self-grades, implementation narratives, and persuasive rationale explaining why the code is safe or why edge cases were skipped. Instruct the advisor: "AuditARTIFACTstrictly againstCONTRACTand caller/guard context. Cite concretefile:linelocations and a triggering input/scenario for every defect. Zero findings is a valid result; do not invent findings."
- Run the selected backend via
stdin(< "$tmpfile") using the read-only sandbox invocation above, thenrm -f "$tmpfile". - Reconcile every advisor finding using the 4-Tier
RECONCILEPrecedence:- (1) Contract gap: exposes a real ambiguity, contradiction, or missing safety boundary in the spec/plan/invariants -> escalate to the user or amend the contract (
criteria_revision+steer) before proceeding. - (2) Actionable defect: proven bug, regression, security flaw, or unmet criterion with a concrete trigger -> classify as
needs-fixand repair the root cause. - (3) Explicit Ruling: non-defect engineering tradeoff within the stated load/scope ceiling -> record
Ruling: <decision> — <why> — <cost_if_wrong>instead of churning code. - (4) Context noise: false positive disproved by repository
file:lineevidence, callers, or runtime guards -> dismiss with the falsifyingfile:linecitation.
- (1) Contract gap: exposes a real ambiguity, contradiction, or missing safety boundary in the spec/plan/invariants -> escalate to the user or amend the contract (
- Doubt/Review Theater Circuit Breaker: if
>= 2consecutive--doubtor review cycles return prose critiques ("substantive findings") with0findings passing Tier 1 or Tier 2, stop re-spinning and either close out via an explicit Tier 3Ruling:(withcost_if_wrong) or escalate to the user.
Artifact requirement
After running, save a reusable markdown artifact to:
# Standard mode:
.omagy/artifacts/ask-<backend>-<slug>-<YYYYMMDDTHHMMSSZ>.md
# --doubt mode:
.omagy/artifacts/ask-<backend>-doubt-<slug>-<YYYYMMDDTHHMMSSZ>.mdMinimum sections (redact all secrets, API keys, Bearer/CLI tokens, and credentials from both the recorded prompt/packet and CLI output before saving .omagy/artifacts/ask-*.md):
- Original user task / target and mode (
standardor--doubt) - Backend, read-only invocation command, and redacted prompt / Blind-Claim Packet sent via
stdin - Redacted raw CLI output
- 4-Tier
RECONCILEdisposition table (--doubt) or concise synthesis (standard) - Action items / next steps
Then report the synthesis and action items to the user, stating explicitly where you agree or disagree with the advisor backed by file:line or command evidence.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

