Agent skill

Ask

by sd0xdev in sd0xdev/sd0x-harness

Context-aware Q&A with auto context gathering. An agent skill from sd0xdev/sd0x-harness.

MITAuto-check: notesDevelopment

Install Ask

skills CLI
$ npx skills add sd0xdev/sd0x-harness --skill ask -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sd0xdev/sd0x-harness ask --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ask .claude/skills/ask && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ask
GitHub stars
192
Token cost
~2.1k tokens
SKILL.md length
830 words
Files
3 (incl. references)
Skills in repo
91
Repo updated
First seen
Licence
MIT

At a glance

Context-aware Q&A with auto context gathering. An agent skill from sd0xdev/sd0x-harness.

  • Works in 5 steps: Session Context Capture → Intent Classification + Routing → Context Gathering → …
  • : user has a quick question about codebase
  • SKILL.md covers Trigger, When NOT to Use, Procedure and Read-Only Enforcement, plus 5 more sections
  • Calls git

What it does

Ask is an agent skill from sd0xdev/sd0x-harness. Context-aware Q&A with auto context gathering. Use when: user has a quick question about codebase, git history, rules, docs, or skills during development. Not for: code changes (use feature-dev), code review (use codex-review-fast), deep research (use deep-research), full code trace (use code-explore). Output: structured answer with source attribution.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/intent-patterns.md` and `references/routing-table.md`).

It sits in Development, covering Deep research and Git workflow. It works with Git and Bash. The repository describes itself as: The harness layer for Claude Code — a reference implementation of harness engineering with hook-enforced dual review, state-machine gates that survive context compaction, and… The licence is MIT.

When your agent uses it

  • : user has a quick question about codebase
  • Skills during development

Example prompts

  • “/ask”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash(git:*), Bash(node:*), Agent

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Session Context Capture
  2. Intent Classification + Routing
  3. Context Gathering
  4. Sub-Agent Dispatch (Optional)
  5. Answer Synthesis

What it can do on your machine

Read from SKILL.md and the folder at commit c9a2036. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Bash(git:*)
    • Bash(node:*)
    • Agent

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ask loads about 2.1k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 830 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:138
    | Secret skip | Do not read `.env`, `credentials.*`, `*secret*` files |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sd0xdev/sd0x-harness at commit c9a2036, republished under its MIT licence (© sd0xdev). 830 words, ~2,093 tokens.

Download SKILL.mdSave it as .claude/skills/ask/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
ask
description
Context-aware Q&A with auto context gathering. Use when: user has a quick question about codebase, git history, rules, docs, or skills during development. Not for: code changes (use feature-dev), code review (use codex-review-fast), deep research (use deep-research), full code trace (use code-explore). Output: structured answer with source attribution.
allowed-tools
Read, Grep, Glob, Bash(git:*), Bash(node:*), Agent

Ask — Context-Aware Q&A

Trigger

  • Keywords: ask, quick question, context question, project question, 問一下, 想了解, 想知道

When NOT to Use

ScenarioAlternative
Code modification or implementation/feature-dev
Code review or PR review/codex-review-fast
Tech spec review/review-spec
Document review/codex-review-doc
Bug fixing/bug-fix
Next step decision/next-step
Deep multi-source research/deep-research
Systematic code tracing/code-explore

Procedure

Phase 0: Session Context Capture

Run these 4 commands in parallel to build session context:

#ActionTool
1Current branchBash("git branch --show-current")
2Feature detectionBash("node scripts/resolve-feature.js") — the wrapper, not the CLI: it owns the failure payload, so a resolver that runs and fails — nonzero exit, signal, truncated write, off-contract payload — still yields the full shape with scan_error: true rather than {} or a truncated document. A missing node yields no JSON at all; treat that like any other unusable payload
2bscan_error gatescan_error !== false ⇒ the source sets are unknown, not empty — report and take the ⚠️ Need Human exit rather than answering from an empty set. Gate on !== false, not === true: a {} payload from a shell fallback has no such field, so a non-null key is not evidence the sets are complete
3Changed filesBash("git status --porcelain")
4Recent commitsBash("git log --oneline -5")

Untracked file fallback: If feature resolver returns key: null, derive feature from changed/untracked paths:

  1. Parse git status --porcelain output for docs/features/<key>/ or skills/<key>/ patterns
  2. Extract <key> as candidate feature
  3. Use this for docs intent feature-first lookup when resolver fails
Phase 1: Intent Classification + Routing
1a. Conversation Context Integration

Before classifying intent, review prior conversation turns for:

  • Active feature: feature being developed, files recently discussed or edited
  • Ongoing task: what skill was last invoked, what phase we are in
  • Implicit scope: if the user asks "why?" after a code change, the scope is that change

Use this context to disambiguate the question and select the right intent. See references/intent-patterns.md for edge cases.

1b. Intent Classification

Classify the question (LLM-inferred) into one or more intents:

IntentSignal ExamplesContext Actions
code"function X 做什麼", file paths, module namesGrep → Read → trace 1 level
git"最近改了什麼", "誰改的", "when"git log / diff / blame
docs"需求是什麼", "spec 寫了什麼"Feature resolve → source set by question kind → fallback Glob
rules"規則是什麼", "convention", "allowed"Read rules/ files
skill"有沒有 skill", "怎麼用 /X"Glob skills/ → Read SKILL.md
arch"系統架構", "整體設計"CLAUDE.md + Explore agent
multiMultiple intents mixedCombine actions from each intent
1c. Skill Routing Check

Before gathering context, check if the question is action-oriented. See references/routing-table.md.

If a better skill is identified, suggest it: "這個問題更適合 /X,要改用嗎?" — do not auto-redirect.

Show full SKILL.md (405 more words)Show less
Phase 2: Context Gathering

Execute per-intent tool call sequences. Hard limits apply.

code: Grep keywords (top 10 files) → Read most relevant (max 5) → trace imports (1 level)

git: git log --oneline -20 → git diff (if recent changes) → git blame (if specific lines)

docs: Resolve feature → pick the source set the question actually asks for → fallback Glob "docs/**/*.md" (top 5) → Read (max 3)

The question is…ReadNot
"現在的行為是什麼"code, rules/, current_authorityA tech spec — it records the design, not what shipped
"當初為什麼這樣設計"design_records—
"當初要求什麼 / 這張單結了嗎"work_records—
"這個決定是什麼時候做的"history_records—

Answering a current-behaviour question from a design record is the specific failure this split exists to prevent: the spec is the older artifact, so it reads as authoritative and is wrong. When a design record is the only source available, say which document the answer came from and that it may predate the code.

rules: Glob rules/*.md + .claude/rules/*.md → Grep keywords → Read + quote (max 3)

skill: Glob skills/*/SKILL.md → Grep keywords (top 5) → Read (max 3)

arch: Read CLAUDE.md + key entrypoints → dispatch Explore agent

multi: Combine steps from each intent. Parallel execution. Hard limit: max 8 file reads total.

Phase 3: Sub-Agent Dispatch (Optional)
ComplexityCriteriaStrategy
SimpleSingle intent, clear target, < 5 filesDirect tools only (0 agents)
MediumMulti-file, cross-module1 Explore agent
ComplexMulti-intent, cross-cutting2 agents parallel (hard max)

Dispatch when: Grep returns > 10 files across modules, or question involves architecture / cross-cutting concerns. Default: direct tool calls.

Phase 4: Answer Synthesis

Combine all gathered context into a structured answer. Follow the output format below.

Read-Only Enforcement

This skill is strictly read-only. The following git commands are prohibited:

git add | git commit | git push | git pull | git reset | git stash
git rebase | git merge | git checkout -- | git restore | git clean

allowed-tools does not include Edit, Write, or NotebookEdit.

Path Security

ControlRule
Repo boundaryAll Read/Glob within repo root (git rev-parse --show-toplevel)
Traversal rejectionReject .. path segments, absolute paths outside repo, symlinks out of repo
Secret skipDo not read .env, credentials.*, *secret* files
Output redactionHigh-confidence secret patterns → [REDACTED]; medium-confidence → mask with 4 chars visible

Output Format

markdown
## Answer

{Direct, concise answer}

### Sources

| Type | Reference | Relevance |
|------|-----------|-----------|
| file | `path/file.js:42` | {why relevant} |
| commit | `abc1234 — message` | {why relevant} |
| command | `git log --oneline -5` | {result summary} |

### See Also

- `/code-explore` — for full trace
- {other relevant skill or doc}

Every claim must have at least one source evidence. Answer < 500 words unless user requests detail.

Verification

  • Session context captured (branch, feature, changed files)
  • Intent classified and context gathered per pipeline
  • Source attribution present for all claims
  • No Edit/Write/mutating git commands executed
  • No secrets in output

References

  • references/intent-patterns.md — Detailed intent examples and edge cases (read when classifying ambiguous questions)
  • references/routing-table.md — Full skill routing decision table (read when checking if another skill is better)

Examples

Code Question
Input: /ask resolve-feature-cli.js 怎麼偵測 feature?
Phase 0: branch=feat/ask, feature=ask
Phase 1: Intent=code (file path mentioned)
Phase 2: Grep "resolve-feature" → Read scripts/lib/feature-resolver.js → trace exports
Phase 4: Answer with Sources (file evidence)
Git Question
Input: /ask 最近有什麼 commit?
Phase 0: branch=feat/ask
Phase 1: Intent=git ("最近", "commit")
Phase 2: git log --oneline -20
Phase 4: Answer with Sources (commit + command evidence)
Multi-Intent Question
Input: /ask auto-loop 的規則是什麼?有哪些 skill 會用到?
Phase 0: branch=feat/ask
Phase 1: Intent=multi (rules + skill)
Phase 2: Read rules/auto-loop.md + Grep "auto-loop" in skills/*/SKILL.md
Phase 4: Answer with Sources (file evidence from both rules and skills)

© sd0xdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/ask of sd0xdev/sd0x-harness.

  • SKILL.md
  • references/intent-patterns.md
  • references/routing-table.md

Open the folder on GitHubat commit c9a2036

Compare with similar skills

Ask next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ask compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ask this skillsd0xdev/sd0x-harness192—~2.1kAutomated safety check: NotesMIT
Wednesday Gitwednesday-solutions/ai-agent-skills170—~702Automated safety check: PassMIT
Speckit Git Featurekunstmusik/blue1544 repos~861Automated safety check: PassGPL-3.0
Trace And Isolaterohitg00/skillkit1.5k—~1.8kAutomated safety check: PassApache-2.0
Speckit Git Initializekunstmusik/blue1545 repos~438Automated safety check: PassGPL-3.0
Tapd Iteration InitTencentBlueKing/bk-bcs840—~1.3kAutomated safety check: PassCustom licence

Similar skills

  • Wednesday Git

    wednesday-solutions/ai-agent-skills

    Unified Git workflow. An agent skill from wednesday-solutions/ai-agent-skills.

    170 GitHub stars~702 tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • Speckit Git Feature

    kunstmusik/blue

    Create a feature branch with sequential or timestamp numbering

    154 GitHub starsUsed in 4 repos~861 tokens
    DevelopmentAuto-check passed
  • Trace And Isolate

    rohitg00/skillkit

    Applies systematic tracing and isolation techniques to pinpoint exactly where a bug originates in code.

    1.5k GitHub stars~1.8k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • Speckit Git Initialize

    kunstmusik/blue

    Initialize a Git repository with an initial commit. An agent skill from kunstmusik/blue.

    154 GitHub starsUsed in 5 repos~438 tokens
    DevelopmentAuto-check passed
  • Tapd Iteration Init

    TencentBlueKing/bk-bcs

    迭代执行流水线启动器。分三个阶段执行:信息检查(验证 git 环境、获取迭代信息、 解析迭代分支)→ 恢复检测(已有状态文件时判定恢复策略)→ 新流程初始化(创建分支、 迭代目录和 iteration-state.json)。

    840 GitHub stars~1.3k tokensUpdated 13 days ago
    DevelopmentAuto-check passed
  • Official

    Autonomous NeMo-RL research agent workflow for directed hypothesis testing and open-ended discovery.

    3.5k GitHub stars~2.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from sd0xdev/sd0x-harness

All 91 skills in this repo
  • Adr

    sd0xdev/sd0x-harness

    Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/<feature/adr-<NNN-<title.md with a 3-digit zero-padded…

    192 GitHub stars~4.8k tokensUpdated yesterday
    Auto-check passed
  • Load PR Review

    sd0xdev/sd0x-harness

    Load GitHub PR review comments into AI session — analyze, triage, plan.

    192 GitHub stars~4.4k tokensUpdated yesterday
    Auto-check passed
  • Next Step

    sd0xdev/sd0x-harness

    Change-aware next step advisor. An agent skill from sd0xdev/sd0x-harness.

    192 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Obsidian CLI

    sd0xdev/sd0x-harness

    Obsidian vault integration via official CLI. An agent skill from sd0xdev/sd0x-harness.

    192 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Orchestrate

    sd0xdev/sd0x-harness

    Agent-driven workflow orchestration (v1 report-only). An agent skill from sd0xdev/sd0x-harness.

    192 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • PR Comment

    sd0xdev/sd0x-harness

    Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review.

    192 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Ask

What does Ask do?

Context-aware Q&A with auto context gathering. An agent skill from sd0xdev/sd0x-harness. Ask is an agent skill from sd0xdev/sd0x-harness. Context-aware Q&A with auto context gathering.

When should I use Ask?

Ask fits situations like: : user has a quick question about codebase; skills during development.

How do I install Ask in Claude Code?

Run `npx skills add sd0xdev/sd0x-harness --skill ask -a claude-code`. Or copy the skill folder (skills/ask in sd0xdev/sd0x-harness) into .claude/skills/ask in your project. Claude Code loads it when a task matches its description.

How do I install Ask in Codex?

Run `npx skills add sd0xdev/sd0x-harness --skill ask -a codex`. Or copy the skill folder (skills/ask in sd0xdev/sd0x-harness) into .agents/skills/ask in your project. Codex loads it when a task matches its description.

Can I use Ask in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sd0xdev/sd0x-harness --skill ask -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ask, .gemini/skills/ask, .github/skills/ask and .opencode/skills/ask in your project.

What does Ask need to run?

Going by SKILL.md and its folder, Ask needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash(git:*), Bash(node:*), Agent.

Does Ask access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Ask safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Ask use?

Ask is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ask use?

About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Ask?

Skills that share tags, products or a category with Ask: Wednesday Git (wednesday-solutions/ai-agent-skills, 170 stars), Speckit Git Feature (kunstmusik/blue, 154 stars), Trace And Isolate (rohitg00/skillkit, 1.5k stars) and Speckit Git Initialize (kunstmusik/blue, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ask?

sd0xdev (a GitHub user) maintains it in sd0xdev/sd0x-harness, which has 192 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 6, 2026.

Source: sd0xdev/sd0x-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.