What makes Resolve Beagle notable?

1.1K downloads. Trust evidence available

How should Resolve Beagle be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Resolve Beagle

Use as the follow-up to brainstorm-beagle when a spec has an Open Questions section (or quietly carries latent gaps) that need closing before planning or imp... Skill: Resolve Beagle Owner: anderskev Summary: Use as the follow-up to brainstorm-beagle when a spec has an Open Questions section (or quietly carries latent gaps) that need closing before planning or imp... Tags: latest:1.0.3 Version history: v1.0.3 | 2026-06-25T05:40:25.417Z | auto resolve-beagle 1.0.3 - Removed file: skill-card.md - Expanded latent gap detection in SKILL.md to include unconsumed external surfaces

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.1k

Updated

Oct 11, 2026

Version

1.0.3

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.1K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.3release · observed Jun 25, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17b1fzefm8nj8j1sdkzrze7gn83pfrg:resolve-beagle

Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-anderskev-resolve-beagle/snapshot"

Documentation

CLAWHUB

81,251 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: resolve-beagle
description: "Use as the follow-up to brainstorm-beagle when a spec has an Open Questions section (or quietly carries latent gaps) that need closing before planning or implementation can begin. Triggers on: \"resolve the open questions\", \"close the gaps in this spec\", \"research the open items\", \"finalize my spec\", \"make this spec implementation-ready\", \"answer the TBDs\". Also triggers whenever the user points at a brainstorm-beagle spec and asks for research, proposals, or answers to unresolved items. Orchestrates parallel research subagents when available (falls back to inline sequential research otherwise), proposes answers one at a time for user approval, then rewrites the spec in place so it arrives at planning with no known gaps. Does NOT write code, design implementation, or create plans — it only produces a complete spec."
---

# Resolve: Close Spec Gaps

Take a spec produced by `brainstorm-beagle` and close its remaining gaps — both the explicit Open Questions and the latent ones the self-review missed — by researching, proposing answers, and rewriting the spec in place.

The terminal state is a spec with no known open questions and no placeholder requirements. Planning can start immediately after.

<hard_gate>
This skill does not write code, scaffold projects, design architecture, or create implementation plans. It only edits the spec document. "Answering an open question" means proposing a WHAT/WHY answer with rationale — never a HOW. If a question turns out to require implementation design, defer it with a note and move on.
</hard_gate>

## Gates (pass before next step)

Objective pass conditions so steps are not skippable by assertion alone:

1. **Spec located** — The target file path is known and `Read` succeeds (or the user supplied a valid path after you listed 3–5 recent `docs/specs/` candidates).
2. **Gap list published** — One message lists every explicit Open Question bullet **and** each latent gap you will treat as in-scope. **Do not dispatch research** until the user adjusts the list (add/remove/defer) **or** explicitly tells you to proceed with that list.
3. **Research artifact per gap** — Before you present a proposal for gap *G*, you have a structured note for *G*: recommended answer, 1–2 rejected alternatives with reasons, and evidence (file:line, URL, or in-spec citation). No proposal without that artifact.
4. **One proposal queue** — Do not open the next gap’s proposal until the current gap has a clear outcome (accepted, revised wording applied, rejected with what happens next, or deferred with reason).
5. **Rewrite reconciled** — After editing, you read the full spec once and resolve cross-section contradictions; then run the self-review checklist from `../brainstorm-beagle/references/spec-reviewer.md` with failures fixed in-session unless the user opts for a follow-up pass.
6. **Commit** — No `git commit` unless the user answered yes to the commit prompt in § Committing.

## Workflo

_meta.json

{
  "ownerId": "kn79190nfmdb20hk6xjhzt2zv583844x",
  "slug": "resolve-beagle",
  "version": "1.0.3",
  "publishedAt": 1782366025417
}

references/subagent-prompts.md

# Subagent Prompt Templates

Use these when dispatching research tasks to subagents. One task per subagent. Launch all subagents in a single turn so they run in parallel.

Every template ends with the same **return format** — a structured proposal the orchestrator can drop directly into the spec. Don't let subagents return free-form prose; decisions are the deliverable, not transcripts.

## Return format (shared across all templates)

Every subagent must return exactly this structure, ~300 words max:

```
## Recommended answer
<one-sentence answer, then a short paragraph on WHY>

## Alternatives considered
- <alternative 1> — rejected because <reason>
- <alternative 2> — rejected because <reason>

## Evidence
- <file:line citation, URL, or reference to an existing spec section>
- <additional citations as needed>

## Open sub-questions (if any)
- <anything the subagent couldn't resolve and needs the user or orchestrator to decide>
```

If the subagent cannot produce a recommendation with evidence, it should say so explicitly in "Open sub-questions" rather than guess.

---

## Template: Codebase pattern

Use when the question is about how the existing codebase works — an API, a pattern, a file layout, a convention that the spec references.

```
You are researching one question for an in-progress project spec.

Spec path: <absolute path>
Question: <the exact open question, verbatim>

Your job: read the relevant code and return a structured proposal answering the question. Use Grep, Glob, and Read. Do not modify any files.

Scope hints:
- <file/dir hints from the spec, if any>
- <reference points mentioned in the spec>

Return in this exact format:

## Recommended answer
<one-sentence answer, then a short paragraph on WHY — grounded in what you found>

## Alternatives considered
- <alt 1> — rejected because <reason, citing code>
- <alt 2> — rejected because <reason, citing code>

## Evidence
- <file:line> — <one-line description of what's there>
- <file:line> — <one-line description>

## Open sub-questions
- <anything that needs user input or is blocked>

Cap the return at ~300 words. Cite file paths and line numbers. Decisions, not transcripts.
```

## Template: External / API

Use when the question is about an external system — a framework's capabilities, an SDK's API, a tool's behavior.

```
You are researching one question for an in-progress project spec.

Spec path: <absolute path>
Question: <the exact open question, verbatim>

Your job: use web search and page fetch (if web access is available) to find authoritative answers — official docs, source repositories, maintainer statements. Avoid blog posts and secondhand summaries.

Focus area: <framework / SDK / tool name>
Why it matters: <one-line context pulled from the spec's Problem Statement or Key Decisions>

Return in this exact format:

## Recommended answer
<one-sentence answer, then a short paragraph on WHY — grounded in what the official source says>

## Alternatives considered
- <alt 1>

skill-card.md

## Description:

Resolve Beagle helps agents close open questions and latent gaps in a brainstorm-beagle spec by researching issues, proposing evidence-backed answers for user approval, and rewriting the spec in place.

This skill is ready for commercial/non-commercial use.

## Publisher:

[anderskev](https://clawhub.ai/user/anderskev)

### License/Terms of Use:

MIT-0

## Use Case:

Developers, product owners, and spec authors use this skill to turn a brainstorm-beagle spec with open questions, placeholders, or ambiguous requirements into an implementation-ready spec before planning starts.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill can read project files, use external web research, and rewrite the target spec in place.

Mitigation: Use it on specs the agent is allowed to inspect and edit, and review the proposed gap list before allowing research to proceed.

Risk: Accepted proposals could introduce incorrect or misleading requirements into a planning document.

Mitigation: Review each evidence-backed proposal before acceptance and re-read the rewritten spec before planning begins.

Risk: The workflow may create a commit if the user approves it.

Mitigation: Require explicit user approval before any commit and inspect the resulting diff when repository history matters.

## Reference(s):

- [Subagent Prompt Templates](references/subagent-prompts.md)
- [Resolve Beagle ClawHub Listing](https://clawhub.ai/anderskev/skills/resolve-beagle)

## Skill Output:

**Output Type(s):** [Text, Markdown, Guidance, Files]

**Output Format:** [Markdown spec edits with structured proposal text]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Requires user confirmation before research proceeds and before any commit.]

## Skill Version(s):

1.0.3 (source: server release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.