← 返回 Skills 市场
hongyi3

Asking Until 100

作者 Hongyi3 · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ✓ 安全检测通过
222
总下载
1
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install asking-until-100
功能描述
Repo-aware questioning protocol for OpenClaw that increases clarification before acting on coding, project-build, architecture, debugging, and implementation...
使用说明 (SKILL.md)

Asking Until 100

Overview

Use this skill to slow down execution when the task is underspecified, risky, or expensive to get wrong. Treat "100" as target readiness to proceed, not literal certainty.

Workflow

  1. Load explicit instructions and repo-local config such as .asking-until-100.yaml.
  2. Classify the task as coding, build, architecture, debugging, discovery, or general.
  3. Inspect the repo when it looks relevant so repo-discoverable facts do not turn into avoidable questions.
  4. Estimate readiness from the configured dimensions in references/protocol.md.
  5. Choose a questioning mode:
    • fast for low ambiguity
    • guided for moderate ambiguity
    • deep for higher ambiguity or requested rigor
    • report for highest-rigor coding and build tasks with decision-critical gaps
  6. Ask the highest-value questions before taking action.
  7. Respect the execution gate:
    • highest-rigor coding and build tasks default to blocking clarification
    • other tasks default to explicit assumptions when gaps remain

Questioning Style

  • Prefer structural, directional, and decision-shaping questions over generic filler.
  • Use a working hypothesis when it helps the user react to a proposed path.
  • Offer suggested answers when useful, but always leave a free-form path.
  • Do not ask for facts that can be inspected directly from the repo.

High-Rigor Report

For highest-rigor coding or build tasks, begin with Provisional Project Structure, then emit: Working Hypothesis, Architecture Questions, Product Questions, Constraint Questions, and Decision-Critical Unknowns.

The working-hypothesis section must also summarize the execution gate and blocking dimensions.

See references/coding-report-format.md for the required output order and scripts/render_project_structure.py for deterministic structure rendering.

References

  • references/protocol.md for readiness, repo-aware escalation, and stop conditions
  • references/config.md for config fields, precedence, and asking-intensity behavior
  • references/question-patterns.md for question quality rules and option patterns
  • references/coding-report-format.md for the high-rigor report contract
  • references/build-playbook.md for build-specific gaps to check before acting

Scripts And Assets

  • scripts/validate_config.py validates profile files
  • scripts/preview_question_report.py previews questioning output for a prompt
  • scripts/render_project_structure.py renders prompt-only or repo-aware provisional structures
  • scripts/explain_profile_merge.py shows the effective merged profile
  • assets/ contains bundled profiles tuned for gpt-5.4 with xhigh reasoning assumptions

Keep this file concise. Use the references for detailed policy, config, and output examples.

安全使用建议
This skill appears to do what it claims: inspect the local repo and produce structured clarification questions and reports before making changes. Before installing or enabling it: (1) review any repo-local .asking-until-100.yaml you may have to ensure it doesn't contain secrets or sensitive tokens, (2) glance through the bundled scripts (render_project_structure.py, planner.py, validate_config.py) to confirm they only read local files (they do) and do not call external networks, and (3) be aware that the agent may read your workspace files when you invoke this skill — avoid storing sensitive credentials in the repo if you don't want them inspected. If the skill later requested network endpoints, environment tokens, or an install hook that downloads code, re-evaluate as those would be out-of-scope for a questioning/reporting tool.
功能分析
Type: OpenClaw Skill Name: asking-until-100 Version: 0.1.0 The 'asking-until-100' skill bundle is a meta-protocol designed to increase AI agent reliability by enforcing a clarification phase before task execution. The Python scripts (planner.py, render_project_structure.py) implement logic for repository inspection and task classification using safe practices, such as yaml.safe_load and non-recursive directory walking limited to metadata. There is no evidence of data exfiltration, network activity, or malicious execution; rather, the instructions in SKILL.md and the reference documents act as a defensive measure by requiring the agent to verify requirements and repo context before proceeding.
能力评估
Purpose & Capability
The name/description (repo-aware questioning for coding/build tasks) matches the included assets and scripts: planner.py, render_project_structure.py, preview/validate scripts, and bundled profiles. There are no unrelated requirements (no cloud credentials, no system-level config paths) that would contradict the stated purpose.
Instruction Scope
SKILL.md explicitly instructs the agent to load repo-local config (e.g. .asking-until-100.yaml), inspect the repo when relevant, and generate structured question reports. The shipped scripts implement repo inspection, profile merging, structure rendering, and validation. The instructions and code reference only local repo files and bundled profile assets; they do not attempt to read unrelated system state, secrets, or external endpoints.
Install Mechanism
No install spec is provided (instruction-only), and all code is bundled with the skill. There are no downloads or external installers referenced in the manifest, so nothing arbitrary is fetched at install time.
Credentials
The skill declares no required environment variables or primary credential. The code and profiles include references to a 'secrets' readiness dimension but do not request or access environment secrets directly. The requested inputs are proportional to a repo-aware questioning tool.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent or elevated privileges, and there is no indication it modifies other skills or system-wide agent settings.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install asking-until-100
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /asking-until-100 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v0.1.0
- Initial release of the "asking-until-100" skill for OpenClaw. - Introduces structured questioning protocol to clarify tasks before execution, focusing on coding, build, architecture, and debugging. - Implements readiness estimation and adjustable questioning modes (fast, guided, deep, report) based on ambiguity and rigor. - Enforces high-rigor question reports for critical coding/build tasks, including provisional project structure and decision-critical unknowns. - Integrates repo awareness to avoid unnecessary questions and references supporting scripts and configuration options.
元数据
Slug asking-until-100
版本 0.1.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

Asking Until 100 是什么?

Repo-aware questioning protocol for OpenClaw that increases clarification before acting on coding, project-build, architecture, debugging, and implementation... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 222 次。

如何安装 Asking Until 100?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install asking-until-100」即可一键安装,无需额外配置。

Asking Until 100 是免费的吗?

是的,Asking Until 100 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Asking Until 100 支持哪些平台?

Asking Until 100 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Asking Until 100?

由 Hongyi3(@hongyi3)开发并维护,当前版本 v0.1.0。

💬 留言讨论