Creator · skymanbp
Last updated · Sep 4, 2026
Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes per node until stable convergence (no new high-verdict branches over the last 2 rounds + all 12 framings exercised + all leaves complete). Width × depth × ro
Creator · skymanbp
Last updated · Sep 4, 2026
Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes per node until stable convergence (no new high-verdict branches over the last 2 rounds + all 12 framings exercised + all leaves complete). Width × depth × ro
Creator · skymanbp
Last updated · Sep 4, 2026
Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes per node until stable convergence (no new high-verdict branches over the last 2 rounds + all 12 framings exercised + all leaves complete). Width × depth × ro
Creator · skymanbp
Last updated · Sep 4, 2026
Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes per node until stable convergence (no new high-verdict branches over the last 2 rounds + all 12 framings exercised + all leaves complete). Width × depth × ro
Sandbox only
Install targets
Codex install prompt
Install the "tree" agent skill from https://github.com/skymanbp/cc-tree/tree/main/skills/tree. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes per node until stable convergence (no new high-verdict branches over the last 2 rounds + all 12 framings exercised + all leaves complete). Width × depth × rounds default to ∞; resource caps are opt-in. Hard ban on `defer / future-work / TODO / NEEDS-MORE-INFO` leaves — every leaf must be fully derived before counting. Use when 用户说 "brainstorm" / "attack" / "design exploration" / "code audit" / "explore options" / "find what's wrong" / "what should we build" / "tree of thoughts" / 想做穷尽的发散探索 / 想做多角度审查 / 想对一个工件 adversarial critique / 想做设计空间探索. Prefer the per-preset commands (`/cc-tree:brainstorm`, `/cc-tree:attack`, `/cc-tree:design`, `/cc-tree:code-audit`) when the use-case matches; call this skill directly with `--preset <name|path>` to override or supply a custom preset. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"skymanbp-tree","task":"Install tree","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add skymanbp/cc-tree --skill tree
Maintenance
fresh
3d since push
Risk
Needs review
Permission surface may require sandboxing
GitHub quality
107
67/100 Quality · 77/100 Trust
Coverage tags
Review notes
Permission surface may require sandboxing · Financial research output is not financial advice; require human review before any live investment decision
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
107 GitHub stars
Repo activity
107 stars, 0 forks
Maintenance
3d since push
License
MIT
Install
npx skills add skymanbp/cc-tree --skill tree
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add skymanbp/cc-tree --skill treeDo not use when
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20tree%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20tree%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/skymanbp-tree/install
Agent should check
Copy prompt
Task: Use tree in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20tree%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/skymanbp-tree/install
Install command: npx skills add skymanbp/cc-tree --skill tree
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/skymanbp-tree/install
LLM text format
/api/skills/skymanbp-tree/install?format=text
Find alternatives
/api/skills/search?q=tree&limit=3
Agent prompt
Use tree for this task. Review https://www.openagentskill.com/api/skills/skymanbp-tree/install, then install with: npx skills add skymanbp/cc-tree --skill treeRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/skymanbp-tree
LLM text
/api/registry/manifest/skymanbp-tree?format=text
Install alias
/api/registry/install/skymanbp-tree
Recommend
/api/registry/recommend?task=Use%20tree%20in%20an%20agent%20workflow&limit=3
Agent fit
Local desktop
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Local desktop
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO107 GitHub stars
Stars/forks activity
CHECK107 stars, 0 forks; issue activity unavailable in current metadata
Recent maintenance
PASS3d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Operate local tools
I need my agent to operate local files and desktop apps in a repeatable workflow.
Search private knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: tree description: Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes per node until stable convergence (no new high-verdict branches over the last 2 rounds + all 12 framings exercised + all leaves complete). Width × depth × rounds default to ∞; resource caps are opt-in. Hard ban on `defer / future-work / TODO / NEEDS-MORE-INFO` leaves — every leaf must be fully derived before counting. Use when 用户说 "brainstorm" / "attack" / "design exploration" / "code audit" / "explore options" / "find what's wrong" / "what should we build" / "tree of thoughts" / 想做穷尽的发散探索 / 想做多角度审查 / 想对一个工件 adversarial critique / 想做设计空间探索. Prefer the per-preset commands (`/cc-tree:brainstorm`, `/cc-tree:attack`, `/cc-tree:design`, `/cc-tree:code-audit`) when the use-case matches; call this skill directly with `--preset <name|path>` to override or supply a custom preset. disable-model-invocation: false argument-hint: "<root> --preset <name|path> [--lang <tag|auto>] [--width N|∞] [--depth N|∞] [--rounds N|conv] [--max-branches N|∞] [--out <dir>] [--glossary <path>] [--field <name|path>] [--seed-from <primary.md>] [--no-grill] [--no-online] [--min-frameworks N] [--min-novelty-ratio R] — `<root>` is a topic string, file path, problem statement, or design prompt; `--preset` is required (use `brainstorm` / `attack` / `design` / `code-audit` for shipped presets, or a path to your own .md)" ---
# tree — universal radial-tree exploration engine
> **What this skill is.** A single engine implementing recursive > radial-tree exploration (root → 12-framing expansion → per-node > 12-field derivation → score → recurse on high-verdict leaves → > terminate on **substantive convergence**). What varies between > use-cases (brainstorm vs critique vs design vs code-audit) is the > baseline recipe, node schema, scoring dimensions, and verdict > vocabulary — all parameterized via a **preset** file.
> **What this skill is NOT.** Not a one-shot LLM call that returns a > bulleted list. Not a chat interface — once `/cc-tree:tree` is > invoked, the engine runs to convergence without further prompts. > Not bundled with a model — pure prompt-engineering on top of Claude > Code's existing model setting.
The full engine specification lives in [`docs/ENGINE.md`](../../docs/ENGINE.md). This SKILL.md is a 7-step navigation guide; **Read `docs/ENGINE.md` before producing the first node** (the engine spec is what defines "valid" for everything you'll write).
---
## 1. Invocation
``` /cc-tree:tree <root> --preset <name|path> [flags] ```
**`<root>`** is preset-typed: - `brainstorm` preset → topic string, e.g. `"ways to detect dark-matter substructure"` - `attack` preset → file path (`.md` / `.tex` / etc.) or quoted argument-text - `design` preset → design-prompt string or `.md` file path - `code-audit` preset → file path or directory path
**`--preset`** is required: - Built-in: `brainstorm`, `attack`, `design`, `code-audit` (resolve to `presets/<name>.md` in this plugin) - Path: `./my-custom.md` (any .md file with the right frontmatter)
### Common flags (apply across presets)
| Flag | Default | Meaning | |---|---|---| | `--lang <tag\|auto>` | **en** | Output language for all localized prose (node statements, derivations, report narrative, warnings). Machine tokens — flag/command names, frontmatter & JSON keys, `root_kind` values, verdict labels, status tokens, filenames — always stay English. `<tag>` is a BCP-47-like code (`en`, `zh`, `zh-Hans`, `zh-Hant`, `fr-CA`); `zh` = Simplified Chinese, `zh-Hant` = Traditional. `auto` detects the dominant language of `<root>` and falls back to `en` for mixed / path-only / code-only input. Resolved **once before preset load**, recorded in run metadata (`language_request` / `output_language` / `language_source`), and never prompted mid-run. Full precedence, resume, and chain semantics: [`docs/ENGINE.md §1.0`](../../docs/ENGINE.md#10-output-language-resolution-and-schema-boundary). | | `--width N` | **∞** | Cap on final leaf count (the outer arc of the tree). `∞` / `inf` / unspecified all mean unlimited. | | `--depth N` | **∞** | Cap on tree depth from root. | | `--rounds N` | `conv` | Cap on expansion rounds. `conv` = no cap; terminate by §6 substantive convergence. | | `--max-branches N` | **∞** | Cap on new branches per node per round. **Floor is 12** because §3 requires all 12 framings to fire; this flag only raises the ceiling. | | `--out <dir>` | `tree-out/<UTCdate>__<slug>/` | Output directory. Per-preset commands override (e.g. `brainstorm-out/`). | | `--glossary <path>` | (preset-determined) | Path to a glossary / FACTS.md / glossary section in a dossier; used by §2.0 grill prelude. | | `--field <name\|path>` | (none) | Field profile for domain-aware reviewer weighting. `<name>` → `field-profiles/<name>.md` in this plugin; `<path>` → a literal file. Feeds §3.C / §3.D / §3.I / §3.J + the §3.X / §4 evidence bar. Missing profile → warn + continue (non-blocking). See [`docs/ENGINE.md` §2.2](../../docs/ENGINE.md#22-field-profile-optional---field-namepath). | | `--seed-from <primary.md>` | (none) | Seed the tree from a prior run's primary deliverable (`shortlist.md` / `options.md` / `confirmed.md`): each listed item enters as a depth-1 seed node and is re-expanded. The substrate for cross-preset chaining ([`docs/chaining.md`](../../docs/chaining.md)). Alias: `--from-prior`. | | `--no-grill` | off | Skip §2.0 glossary grill prelude. Marks root-node terms as `unverified`; §6 convergence adds a warning. | | `--no-online` | off | Disable `WebSearch` / `WebFetch`. Local + already-Read references only. | | `--min-frameworks N` | 12 | Minimum framing passes per node. **Floor is 12** (full §3.A–§3.L); flag exists for documentation, not relaxation. | | `--min-novelty-ratio R` | 0.15 | §6.1 condition 2 requires "last 2 rounds' high-verdict / total < R". |
> Presets and their command wrappers may document additional > preset-specific flags (e.g. `attack`'s > `--focus <section|claim|equation>`); a flag documented by the active > preset or its wrapper is not "unknown" (`docs/ENGINE.md` §1.3).
> Caps default to ∞ on purpose. The intended termination is §6 > substantive convergence — see [`docs/ENGINE.md §6`](../../docs/ENGINE.md#6-6-convergence). > Caps are escape valves for quick exploration; when one trips, the > engine still drives every in-flight node to a complete state before > reporting `WIDTH_CAP_REACHED` / `DEPTH_CAP_REACHED` / > `ROUNDS_EXHAUSTED`.
---
## 2. Execution flow
> **Required Reads at session start** (before producing the first node): > 1. The preset file (`presets/<name>.md` or `--preset <path>`) — full file. > 2. [`docs/ENGINE.md`](../../docs/ENGINE.md) — full file. This is the contract. > 3. [`docs/framings.md`](../../docs/framings.md) — the 12 framings with per-preset > examples. > 4. If `--glossary <path>`: Read that glossary file in full.
### Step 1 — Preset load
Open the preset file. Extract from its YAML frontmatter: - `name`, `description`, `use-when` (informational) - `root_kind` — `topic | artifact | code | design-prompt` - `subject_label` — what each tree node is called (`idea`, `critique`, `option`, `audit-finding`, …) - `verdict_enum` — 4-tuple: `advances / kept / pruned / blocked` - `convergence_metric` — which verdict *role* counts toward the §6.1 condition-2 ratio. It must be one of the four `verdict_enum` role keys verbatim (`advances` / `kept` / `pruned` / `blocked`); alias spellings like `novelty_ratio` are rejected by the validator. All four shipped presets use `advances` ([`docs/presets.md`](../../docs/presets.md)) - `score_dims` — list of 5 scoring dimensions (key + name + desc) - `node_schema` — list of 12 node-field names - `output_artifacts` — file names for the per-verdict final reports
The preset body (below frontmatter) supplies: - §2 baseline recipe (what to Read / Grep / WebFetch to build the root) - Optional per-framing examples (§3.A–§3.L flavored for this preset) - Optional anti-pattern list specific to this preset
### Step 2 — §2 baseline
Follow the preset's baseline recipe. For all presets this includes: - §2.0 (unless `--no-grill`): glossary-grill prelude. Lock root-node noun-phrases to the glossary if one was supplied; surface MISSING / AMBIGUOUS / CONFLICT one question at a time per [`docs/ENGINE.md §2.0`](../../docs/ENGINE.md#20-glossary-grill-prelude-mandatory-unless---no-grill). - §2.A or §2.B (preset-determined): build the root node from real evidence (Read files, Grep symbols, WebFetch references). The root must have the 5-8 fields the preset specifies, each with `file:line` or URL evidence.
Save the root to `<out>/tree.md` + `<out>/tree.json` before producing any framing branches.
### Step 3 — §3 framing pass (12 passes per node)
For each node (starting with root, then any high-verdict leaf in the next round):
Run §3.A through §3.L, each producing **at least 1** new child branch. See [`docs/framings.md`](../../docs/framings.md) for the full prompt per framing, including domain-specific examples per preset.
**Parallelize when fan-out ≥ 5** (always true for the root and hot leaves): dispatch the 12 framings across `Agent(Explore)` sub-agents per the mandatory protocol in [`docs/ENGINE.md` §8.1](../../docs/ENGINE.md#81-sub-agent-dispatch-mandatory-when-a-nodes-expected-fan-out--5). Running them sequentially at that fan-out is a defect. Deep marginal leaves (< 5 expected children) may run sequentially.
§3.X (if `--no-online` is off): per node, do 1 round of `WebSearch` + `WebFetch`. **The query set is preset-determined** (brainstorm/design → prior art + tooling; attack → critiques / errata; code-audit → CVEs / advisories) — see [`docs/framings.md`](../../docs/framings.md) §3.X.
### Step 4 — §4 per-branch 12-field derivation
For each branch produced in §3, fill the preset's 12 node-field schema. Field requirements live in [`docs/ENGINE.md §4`](../../docs/ENGINE.md#4-4-per-node-derivation-12-field-schema). Hard rules: - No field may contain `应该 / 大概 / probably / maybe / 也许` — the field is invalid and must be rewritten. - No field may contain `defer / future work / TODO / FIXME / 略 / details omitted / 待定 / NEEDS-MORE-INFO`-style placeholders — the node is forced to `INCOMPLETE_FORBIDDEN` and **must** be driven to completion before counting. - Numerical claims require a one-shot `python (sympy/numpy)` sanity check via `Bash` — output pasted into the field. - External references require `WebFetch` of the actual arXiv abs / DOI / spec page; `WebSearch` snippets are not sufficient.
Append the filled node to `tree.md` + `tree.json` immediately (incremental write — see §7 for crash-safety contract).
### Step 5 — §5 scoring and verdict
Score the node along the preset's 5 dimensions (each 0–3, integer). Sum = `score` (max 15). Map score → verdict via the preset's `verdict_enum` and the preset-specific rule (e.g. brainstorm: `score ≥ 11 ∧ no [NEEDS_VERIFICATION] → PROMISING`; attack: `score ≥ 11 ∧ artifact_defense empty → CONFIRMED`).
Sibling merging (§5.4): any two siblings with cosine similarity ≥ 0.85 on their idea / critique / option / finding statement → merge, keep the higher-scored one, tag the other `MERGED_INTO=<id>`.
### Step 6 — §6 convergence check
After every round, evaluate the 6 conditions in [`docs/ENGINE.md §6`](../../docs/ENGINE.md#6-6-convergence). All 6 must hold simultaneously to declare `CONVERGED`. If any user-specified `--width / --depth / --rounds` cap trips first, report the appropriate `*_CAP_REACHED` / `ROUNDS_EXHAUSTED` status, but **all leaves must be complete** before stopping.
If neither convergence nor a cap-trip, pick the highest-verdict leaf that hasn't been re-expanded yet, run §3–§5 on it, and loop.
### Step 7 — §7 final report
When termination is declared, write the preset's `output_artifacts` to `<out>/`. For all presets this includes: - `tree.md` — full tree, human-rea
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for tree, ready for a manual X post.
A practical pick for design or creative work: tree: Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes... 107 stars https://www.openagentskill.com/skills/skymanbp-tree?ref=x
Listing + install path for tree: https://www.openagentskill.com/skills/skymanbp-tree?ref=x Install: npx skills add skymanbp/cc-tree --skill tree
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to skymanbp but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/skymanbp-tree?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/skymanbp-tree?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/skymanbp-tree/audit)
[](https://www.openagentskill.com/skills/skymanbp-tree?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)skymanbp
@skymanbp
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsSandbox only
Install targets
Codex install prompt
Install the "tree" agent skill from https://github.com/skymanbp/cc-tree/tree/main/skills/tree. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes per node until stable convergence (no new high-verdict branches over the last 2 rounds + all 12 framings exercised + all leaves complete). Width × depth × rounds default to ∞; resource caps are opt-in. Hard ban on `defer / future-work / TODO / NEEDS-MORE-INFO` leaves — every leaf must be fully derived before counting. Use when 用户说 "brainstorm" / "attack" / "design exploration" / "code audit" / "explore options" / "find what's wrong" / "what should we build" / "tree of thoughts" / 想做穷尽的发散探索 / 想做多角度审查 / 想对一个工件 adversarial critique / 想做设计空间探索. Prefer the per-preset commands (`/cc-tree:brainstorm`, `/cc-tree:attack`, `/cc-tree:design`, `/cc-tree:code-audit`) when the use-case matches; call this skill directly with `--preset <name|path>` to override or supply a custom preset. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"skymanbp-tree","task":"Install tree","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add skymanbp/cc-tree --skill tree
Maintenance
fresh
3d since push
Risk
Needs review
Permission surface may require sandboxing
GitHub quality
107
67/100 Quality · 77/100 Trust
Coverage tags
Review notes
Permission surface may require sandboxing · Financial research output is not financial advice; require human review before any live investment decision
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
107 GitHub stars
Repo activity
107 stars, 0 forks
Maintenance
3d since push
License
MIT
Install
npx skills add skymanbp/cc-tree --skill tree
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add skymanbp/cc-tree --skill treeDo not use when
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20tree%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20tree%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/skymanbp-tree/install
Agent should check
Copy prompt
Task: Use tree in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20tree%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/skymanbp-tree/install
Install command: npx skills add skymanbp/cc-tree --skill tree
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/skymanbp-tree/install
LLM text format
/api/skills/skymanbp-tree/install?format=text
Find alternatives
/api/skills/search?q=tree&limit=3
Agent prompt
Use tree for this task. Review https://www.openagentskill.com/api/skills/skymanbp-tree/install, then install with: npx skills add skymanbp/cc-tree --skill treeRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/skymanbp-tree
LLM text
/api/registry/manifest/skymanbp-tree?format=text
Install alias
/api/registry/install/skymanbp-tree
Recommend
/api/registry/recommend?task=Use%20tree%20in%20an%20agent%20workflow&limit=3
Agent fit
Local desktop
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Local desktop
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO107 GitHub stars
Stars/forks activity
CHECK107 stars, 0 forks; issue activity unavailable in current metadata
Recent maintenance
PASS3d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Operate local tools
I need my agent to operate local files and desktop apps in a repeatable workflow.
Search private knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: tree description: Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes per node until stable convergence (no new high-verdict branches over the last 2 rounds + all 12 framings exercised + all leaves complete). Width × depth × rounds default to ∞; resource caps are opt-in. Hard ban on `defer / future-work / TODO / NEEDS-MORE-INFO` leaves — every leaf must be fully derived before counting. Use when 用户说 "brainstorm" / "attack" / "design exploration" / "code audit" / "explore options" / "find what's wrong" / "what should we build" / "tree of thoughts" / 想做穷尽的发散探索 / 想做多角度审查 / 想对一个工件 adversarial critique / 想做设计空间探索. Prefer the per-preset commands (`/cc-tree:brainstorm`, `/cc-tree:attack`, `/cc-tree:design`, `/cc-tree:code-audit`) when the use-case matches; call this skill directly with `--preset <name|path>` to override or supply a custom preset. disable-model-invocation: false argument-hint: "<root> --preset <name|path> [--lang <tag|auto>] [--width N|∞] [--depth N|∞] [--rounds N|conv] [--max-branches N|∞] [--out <dir>] [--glossary <path>] [--field <name|path>] [--seed-from <primary.md>] [--no-grill] [--no-online] [--min-frameworks N] [--min-novelty-ratio R] — `<root>` is a topic string, file path, problem statement, or design prompt; `--preset` is required (use `brainstorm` / `attack` / `design` / `code-audit` for shipped presets, or a path to your own .md)" ---
# tree — universal radial-tree exploration engine
> **What this skill is.** A single engine implementing recursive > radial-tree exploration (root → 12-framing expansion → per-node > 12-field derivation → score → recurse on high-verdict leaves → > terminate on **substantive convergence**). What varies between > use-cases (brainstorm vs critique vs design vs code-audit) is the > baseline recipe, node schema, scoring dimensions, and verdict > vocabulary — all parameterized via a **preset** file.
> **What this skill is NOT.** Not a one-shot LLM call that returns a > bulleted list. Not a chat interface — once `/cc-tree:tree` is > invoked, the engine runs to convergence without further prompts. > Not bundled with a model — pure prompt-engineering on top of Claude > Code's existing model setting.
The full engine specification lives in [`docs/ENGINE.md`](../../docs/ENGINE.md). This SKILL.md is a 7-step navigation guide; **Read `docs/ENGINE.md` before producing the first node** (the engine spec is what defines "valid" for everything you'll write).
---
## 1. Invocation
``` /cc-tree:tree <root> --preset <name|path> [flags] ```
**`<root>`** is preset-typed: - `brainstorm` preset → topic string, e.g. `"ways to detect dark-matter substructure"` - `attack` preset → file path (`.md` / `.tex` / etc.) or quoted argument-text - `design` preset → design-prompt string or `.md` file path - `code-audit` preset → file path or directory path
**`--preset`** is required: - Built-in: `brainstorm`, `attack`, `design`, `code-audit` (resolve to `presets/<name>.md` in this plugin) - Path: `./my-custom.md` (any .md file with the right frontmatter)
### Common flags (apply across presets)
| Flag | Default | Meaning | |---|---|---| | `--lang <tag\|auto>` | **en** | Output language for all localized prose (node statements, derivations, report narrative, warnings). Machine tokens — flag/command names, frontmatter & JSON keys, `root_kind` values, verdict labels, status tokens, filenames — always stay English. `<tag>` is a BCP-47-like code (`en`, `zh`, `zh-Hans`, `zh-Hant`, `fr-CA`); `zh` = Simplified Chinese, `zh-Hant` = Traditional. `auto` detects the dominant language of `<root>` and falls back to `en` for mixed / path-only / code-only input. Resolved **once before preset load**, recorded in run metadata (`language_request` / `output_language` / `language_source`), and never prompted mid-run. Full precedence, resume, and chain semantics: [`docs/ENGINE.md §1.0`](../../docs/ENGINE.md#10-output-language-resolution-and-schema-boundary). | | `--width N` | **∞** | Cap on final leaf count (the outer arc of the tree). `∞` / `inf` / unspecified all mean unlimited. | | `--depth N` | **∞** | Cap on tree depth from root. | | `--rounds N` | `conv` | Cap on expansion rounds. `conv` = no cap; terminate by §6 substantive convergence. | | `--max-branches N` | **∞** | Cap on new branches per node per round. **Floor is 12** because §3 requires all 12 framings to fire; this flag only raises the ceiling. | | `--out <dir>` | `tree-out/<UTCdate>__<slug>/` | Output directory. Per-preset commands override (e.g. `brainstorm-out/`). | | `--glossary <path>` | (preset-determined) | Path to a glossary / FACTS.md / glossary section in a dossier; used by §2.0 grill prelude. | | `--field <name\|path>` | (none) | Field profile for domain-aware reviewer weighting. `<name>` → `field-profiles/<name>.md` in this plugin; `<path>` → a literal file. Feeds §3.C / §3.D / §3.I / §3.J + the §3.X / §4 evidence bar. Missing profile → warn + continue (non-blocking). See [`docs/ENGINE.md` §2.2](../../docs/ENGINE.md#22-field-profile-optional---field-namepath). | | `--seed-from <primary.md>` | (none) | Seed the tree from a prior run's primary deliverable (`shortlist.md` / `options.md` / `confirmed.md`): each listed item enters as a depth-1 seed node and is re-expanded. The substrate for cross-preset chaining ([`docs/chaining.md`](../../docs/chaining.md)). Alias: `--from-prior`. | | `--no-grill` | off | Skip §2.0 glossary grill prelude. Marks root-node terms as `unverified`; §6 convergence adds a warning. | | `--no-online` | off | Disable `WebSearch` / `WebFetch`. Local + already-Read references only. | | `--min-frameworks N` | 12 | Minimum framing passes per node. **Floor is 12** (full §3.A–§3.L); flag exists for documentation, not relaxation. | | `--min-novelty-ratio R` | 0.15 | §6.1 condition 2 requires "last 2 rounds' high-verdict / total < R". |
> Presets and their command wrappers may document additional > preset-specific flags (e.g. `attack`'s > `--focus <section|claim|equation>`); a flag documented by the active > preset or its wrapper is not "unknown" (`docs/ENGINE.md` §1.3).
> Caps default to ∞ on purpose. The intended termination is §6 > substantive convergence — see [`docs/ENGINE.md §6`](../../docs/ENGINE.md#6-6-convergence). > Caps are escape valves for quick exploration; when one trips, the > engine still drives every in-flight node to a complete state before > reporting `WIDTH_CAP_REACHED` / `DEPTH_CAP_REACHED` / > `ROUNDS_EXHAUSTED`.
---
## 2. Execution flow
> **Required Reads at session start** (before producing the first node): > 1. The preset file (`presets/<name>.md` or `--preset <path>`) — full file. > 2. [`docs/ENGINE.md`](../../docs/ENGINE.md) — full file. This is the contract. > 3. [`docs/framings.md`](../../docs/framings.md) — the 12 framings with per-preset > examples. > 4. If `--glossary <path>`: Read that glossary file in full.
### Step 1 — Preset load
Open the preset file. Extract from its YAML frontmatter: - `name`, `description`, `use-when` (informational) - `root_kind` — `topic | artifact | code | design-prompt` - `subject_label` — what each tree node is called (`idea`, `critique`, `option`, `audit-finding`, …) - `verdict_enum` — 4-tuple: `advances / kept / pruned / blocked` - `convergence_metric` — which verdict *role* counts toward the §6.1 condition-2 ratio. It must be one of the four `verdict_enum` role keys verbatim (`advances` / `kept` / `pruned` / `blocked`); alias spellings like `novelty_ratio` are rejected by the validator. All four shipped presets use `advances` ([`docs/presets.md`](../../docs/presets.md)) - `score_dims` — list of 5 scoring dimensions (key + name + desc) - `node_schema` — list of 12 node-field names - `output_artifacts` — file names for the per-verdict final reports
The preset body (below frontmatter) supplies: - §2 baseline recipe (what to Read / Grep / WebFetch to build the root) - Optional per-framing examples (§3.A–§3.L flavored for this preset) - Optional anti-pattern list specific to this preset
### Step 2 — §2 baseline
Follow the preset's baseline recipe. For all presets this includes: - §2.0 (unless `--no-grill`): glossary-grill prelude. Lock root-node noun-phrases to the glossary if one was supplied; surface MISSING / AMBIGUOUS / CONFLICT one question at a time per [`docs/ENGINE.md §2.0`](../../docs/ENGINE.md#20-glossary-grill-prelude-mandatory-unless---no-grill). - §2.A or §2.B (preset-determined): build the root node from real evidence (Read files, Grep symbols, WebFetch references). The root must have the 5-8 fields the preset specifies, each with `file:line` or URL evidence.
Save the root to `<out>/tree.md` + `<out>/tree.json` before producing any framing branches.
### Step 3 — §3 framing pass (12 passes per node)
For each node (starting with root, then any high-verdict leaf in the next round):
Run §3.A through §3.L, each producing **at least 1** new child branch. See [`docs/framings.md`](../../docs/framings.md) for the full prompt per framing, including domain-specific examples per preset.
**Parallelize when fan-out ≥ 5** (always true for the root and hot leaves): dispatch the 12 framings across `Agent(Explore)` sub-agents per the mandatory protocol in [`docs/ENGINE.md` §8.1](../../docs/ENGINE.md#81-sub-agent-dispatch-mandatory-when-a-nodes-expected-fan-out--5). Running them sequentially at that fan-out is a defect. Deep marginal leaves (< 5 expected children) may run sequentially.
§3.X (if `--no-online` is off): per node, do 1 round of `WebSearch` + `WebFetch`. **The query set is preset-determined** (brainstorm/design → prior art + tooling; attack → critiques / errata; code-audit → CVEs / advisories) — see [`docs/framings.md`](../../docs/framings.md) §3.X.
### Step 4 — §4 per-branch 12-field derivation
For each branch produced in §3, fill the preset's 12 node-field schema. Field requirements live in [`docs/ENGINE.md §4`](../../docs/ENGINE.md#4-4-per-node-derivation-12-field-schema). Hard rules: - No field may contain `应该 / 大概 / probably / maybe / 也许` — the field is invalid and must be rewritten. - No field may contain `defer / future work / TODO / FIXME / 略 / details omitted / 待定 / NEEDS-MORE-INFO`-style placeholders — the node is forced to `INCOMPLETE_FORBIDDEN` and **must** be driven to completion before counting. - Numerical claims require a one-shot `python (sympy/numpy)` sanity check via `Bash` — output pasted into the field. - External references require `WebFetch` of the actual arXiv abs / DOI / spec page; `WebSearch` snippets are not sufficient.
Append the filled node to `tree.md` + `tree.json` immediately (incremental write — see §7 for crash-safety contract).
### Step 5 — §5 scoring and verdict
Score the node along the preset's 5 dimensions (each 0–3, integer). Sum = `score` (max 15). Map score → verdict via the preset's `verdict_enum` and the preset-specific rule (e.g. brainstorm: `score ≥ 11 ∧ no [NEEDS_VERIFICATION] → PROMISING`; attack: `score ≥ 11 ∧ artifact_defense empty → CONFIRMED`).
Sibling merging (§5.4): any two siblings with cosine similarity ≥ 0.85 on their idea / critique / option / finding statement → merge, keep the higher-scored one, tag the other `MERGED_INTO=<id>`.
### Step 6 — §6 convergence check
After every round, evaluate the 6 conditions in [`docs/ENGINE.md §6`](../../docs/ENGINE.md#6-6-convergence). All 6 must hold simultaneously to declare `CONVERGED`. If any user-specified `--width / --depth / --rounds` cap trips first, report the appropriate `*_CAP_REACHED` / `ROUNDS_EXHAUSTED` status, but **all leaves must be complete** before stopping.
If neither convergence nor a cap-trip, pick the highest-verdict leaf that hasn't been re-expanded yet, run §3–§5 on it, and loop.
### Step 7 — §7 final report
When termination is declared, write the preset's `output_artifacts` to `<out>/`. For all presets this includes: - `tree.md` — full tree, human-rea
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for tree, ready for a manual X post.
A practical pick for design or creative work: tree: Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes... 107 stars https://www.openagentskill.com/skills/skymanbp-tree?ref=x
Listing + install path for tree: https://www.openagentskill.com/skills/skymanbp-tree?ref=x Install: npx skills add skymanbp/cc-tree --skill tree
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to skymanbp but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/skymanbp-tree?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/skymanbp-tree?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/skymanbp-tree/audit)
[](https://www.openagentskill.com/skills/skymanbp-tree?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)skymanbp
@skymanbp
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsSandbox only
Install targets
Codex install prompt
Install the "tree" agent skill from https://github.com/skymanbp/cc-tree/tree/main/skills/tree. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes per node until stable convergence (no new high-verdict branches over the last 2 rounds + all 12 framings exercised + all leaves complete). Width × depth × rounds default to ∞; resource caps are opt-in. Hard ban on `defer / future-work / TODO / NEEDS-MORE-INFO` leaves — every leaf must be fully derived before counting. Use when 用户说 "brainstorm" / "attack" / "design exploration" / "code audit" / "explore options" / "find what's wrong" / "what should we build" / "tree of thoughts" / 想做穷尽的发散探索 / 想做多角度审查 / 想对一个工件 adversarial critique / 想做设计空间探索. Prefer the per-preset commands (`/cc-tree:brainstorm`, `/cc-tree:attack`, `/cc-tree:design`, `/cc-tree:code-audit`) when the use-case matches; call this skill directly with `--preset <name|path>` to override or supply a custom preset. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"skymanbp-tree","task":"Install tree","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add skymanbp/cc-tree --skill tree
Maintenance
fresh
3d since push
Risk
Needs review
Permission surface may require sandboxing
GitHub quality
107
67/100 Quality · 77/100 Trust
Coverage tags
Review notes
Permission surface may require sandboxing · Financial research output is not financial advice; require human review before any live investment decision
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
107 GitHub stars
Repo activity
107 stars, 0 forks
Maintenance
3d since push
License
MIT
Install
npx skills add skymanbp/cc-tree --skill tree
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add skymanbp/cc-tree --skill treeDo not use when
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20tree%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20tree%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/skymanbp-tree/install
Agent should check
Copy prompt
Task: Use tree in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20tree%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/skymanbp-tree/install
Install command: npx skills add skymanbp/cc-tree --skill tree
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/skymanbp-tree/install
LLM text format
/api/skills/skymanbp-tree/install?format=text
Find alternatives
/api/skills/search?q=tree&limit=3
Agent prompt
Use tree for this task. Review https://www.openagentskill.com/api/skills/skymanbp-tree/install, then install with: npx skills add skymanbp/cc-tree --skill treeRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/skymanbp-tree
LLM text
/api/registry/manifest/skymanbp-tree?format=text
Install alias
/api/registry/install/skymanbp-tree
Recommend
/api/registry/recommend?task=Use%20tree%20in%20an%20agent%20workflow&limit=3
Agent fit
Local desktop
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Local desktop
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO107 GitHub stars
Stars/forks activity
CHECK107 stars, 0 forks; issue activity unavailable in current metadata
Recent maintenance
PASS3d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Operate local tools
I need my agent to operate local files and desktop apps in a repeatable workflow.
Search private knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: tree description: Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes per node until stable convergence (no new high-verdict branches over the last 2 rounds + all 12 framings exercised + all leaves complete). Width × depth × rounds default to ∞; resource caps are opt-in. Hard ban on `defer / future-work / TODO / NEEDS-MORE-INFO` leaves — every leaf must be fully derived before counting. Use when 用户说 "brainstorm" / "attack" / "design exploration" / "code audit" / "explore options" / "find what's wrong" / "what should we build" / "tree of thoughts" / 想做穷尽的发散探索 / 想做多角度审查 / 想对一个工件 adversarial critique / 想做设计空间探索. Prefer the per-preset commands (`/cc-tree:brainstorm`, `/cc-tree:attack`, `/cc-tree:design`, `/cc-tree:code-audit`) when the use-case matches; call this skill directly with `--preset <name|path>` to override or supply a custom preset. disable-model-invocation: false argument-hint: "<root> --preset <name|path> [--lang <tag|auto>] [--width N|∞] [--depth N|∞] [--rounds N|conv] [--max-branches N|∞] [--out <dir>] [--glossary <path>] [--field <name|path>] [--seed-from <primary.md>] [--no-grill] [--no-online] [--min-frameworks N] [--min-novelty-ratio R] — `<root>` is a topic string, file path, problem statement, or design prompt; `--preset` is required (use `brainstorm` / `attack` / `design` / `code-audit` for shipped presets, or a path to your own .md)" ---
# tree — universal radial-tree exploration engine
> **What this skill is.** A single engine implementing recursive > radial-tree exploration (root → 12-framing expansion → per-node > 12-field derivation → score → recurse on high-verdict leaves → > terminate on **substantive convergence**). What varies between > use-cases (brainstorm vs critique vs design vs code-audit) is the > baseline recipe, node schema, scoring dimensions, and verdict > vocabulary — all parameterized via a **preset** file.
> **What this skill is NOT.** Not a one-shot LLM call that returns a > bulleted list. Not a chat interface — once `/cc-tree:tree` is > invoked, the engine runs to convergence without further prompts. > Not bundled with a model — pure prompt-engineering on top of Claude > Code's existing model setting.
The full engine specification lives in [`docs/ENGINE.md`](../../docs/ENGINE.md). This SKILL.md is a 7-step navigation guide; **Read `docs/ENGINE.md` before producing the first node** (the engine spec is what defines "valid" for everything you'll write).
---
## 1. Invocation
``` /cc-tree:tree <root> --preset <name|path> [flags] ```
**`<root>`** is preset-typed: - `brainstorm` preset → topic string, e.g. `"ways to detect dark-matter substructure"` - `attack` preset → file path (`.md` / `.tex` / etc.) or quoted argument-text - `design` preset → design-prompt string or `.md` file path - `code-audit` preset → file path or directory path
**`--preset`** is required: - Built-in: `brainstorm`, `attack`, `design`, `code-audit` (resolve to `presets/<name>.md` in this plugin) - Path: `./my-custom.md` (any .md file with the right frontmatter)
### Common flags (apply across presets)
| Flag | Default | Meaning | |---|---|---| | `--lang <tag\|auto>` | **en** | Output language for all localized prose (node statements, derivations, report narrative, warnings). Machine tokens — flag/command names, frontmatter & JSON keys, `root_kind` values, verdict labels, status tokens, filenames — always stay English. `<tag>` is a BCP-47-like code (`en`, `zh`, `zh-Hans`, `zh-Hant`, `fr-CA`); `zh` = Simplified Chinese, `zh-Hant` = Traditional. `auto` detects the dominant language of `<root>` and falls back to `en` for mixed / path-only / code-only input. Resolved **once before preset load**, recorded in run metadata (`language_request` / `output_language` / `language_source`), and never prompted mid-run. Full precedence, resume, and chain semantics: [`docs/ENGINE.md §1.0`](../../docs/ENGINE.md#10-output-language-resolution-and-schema-boundary). | | `--width N` | **∞** | Cap on final leaf count (the outer arc of the tree). `∞` / `inf` / unspecified all mean unlimited. | | `--depth N` | **∞** | Cap on tree depth from root. | | `--rounds N` | `conv` | Cap on expansion rounds. `conv` = no cap; terminate by §6 substantive convergence. | | `--max-branches N` | **∞** | Cap on new branches per node per round. **Floor is 12** because §3 requires all 12 framings to fire; this flag only raises the ceiling. | | `--out <dir>` | `tree-out/<UTCdate>__<slug>/` | Output directory. Per-preset commands override (e.g. `brainstorm-out/`). | | `--glossary <path>` | (preset-determined) | Path to a glossary / FACTS.md / glossary section in a dossier; used by §2.0 grill prelude. | | `--field <name\|path>` | (none) | Field profile for domain-aware reviewer weighting. `<name>` → `field-profiles/<name>.md` in this plugin; `<path>` → a literal file. Feeds §3.C / §3.D / §3.I / §3.J + the §3.X / §4 evidence bar. Missing profile → warn + continue (non-blocking). See [`docs/ENGINE.md` §2.2](../../docs/ENGINE.md#22-field-profile-optional---field-namepath). | | `--seed-from <primary.md>` | (none) | Seed the tree from a prior run's primary deliverable (`shortlist.md` / `options.md` / `confirmed.md`): each listed item enters as a depth-1 seed node and is re-expanded. The substrate for cross-preset chaining ([`docs/chaining.md`](../../docs/chaining.md)). Alias: `--from-prior`. | | `--no-grill` | off | Skip §2.0 glossary grill prelude. Marks root-node terms as `unverified`; §6 convergence adds a warning. | | `--no-online` | off | Disable `WebSearch` / `WebFetch`. Local + already-Read references only. | | `--min-frameworks N` | 12 | Minimum framing passes per node. **Floor is 12** (full §3.A–§3.L); flag exists for documentation, not relaxation. | | `--min-novelty-ratio R` | 0.15 | §6.1 condition 2 requires "last 2 rounds' high-verdict / total < R". |
> Presets and their command wrappers may document additional > preset-specific flags (e.g. `attack`'s > `--focus <section|claim|equation>`); a flag documented by the active > preset or its wrapper is not "unknown" (`docs/ENGINE.md` §1.3).
> Caps default to ∞ on purpose. The intended termination is §6 > substantive convergence — see [`docs/ENGINE.md §6`](../../docs/ENGINE.md#6-6-convergence). > Caps are escape valves for quick exploration; when one trips, the > engine still drives every in-flight node to a complete state before > reporting `WIDTH_CAP_REACHED` / `DEPTH_CAP_REACHED` / > `ROUNDS_EXHAUSTED`.
---
## 2. Execution flow
> **Required Reads at session start** (before producing the first node): > 1. The preset file (`presets/<name>.md` or `--preset <path>`) — full file. > 2. [`docs/ENGINE.md`](../../docs/ENGINE.md) — full file. This is the contract. > 3. [`docs/framings.md`](../../docs/framings.md) — the 12 framings with per-preset > examples. > 4. If `--glossary <path>`: Read that glossary file in full.
### Step 1 — Preset load
Open the preset file. Extract from its YAML frontmatter: - `name`, `description`, `use-when` (informational) - `root_kind` — `topic | artifact | code | design-prompt` - `subject_label` — what each tree node is called (`idea`, `critique`, `option`, `audit-finding`, …) - `verdict_enum` — 4-tuple: `advances / kept / pruned / blocked` - `convergence_metric` — which verdict *role* counts toward the §6.1 condition-2 ratio. It must be one of the four `verdict_enum` role keys verbatim (`advances` / `kept` / `pruned` / `blocked`); alias spellings like `novelty_ratio` are rejected by the validator. All four shipped presets use `advances` ([`docs/presets.md`](../../docs/presets.md)) - `score_dims` — list of 5 scoring dimensions (key + name + desc) - `node_schema` — list of 12 node-field names - `output_artifacts` — file names for the per-verdict final reports
The preset body (below frontmatter) supplies: - §2 baseline recipe (what to Read / Grep / WebFetch to build the root) - Optional per-framing examples (§3.A–§3.L flavored for this preset) - Optional anti-pattern list specific to this preset
### Step 2 — §2 baseline
Follow the preset's baseline recipe. For all presets this includes: - §2.0 (unless `--no-grill`): glossary-grill prelude. Lock root-node noun-phrases to the glossary if one was supplied; surface MISSING / AMBIGUOUS / CONFLICT one question at a time per [`docs/ENGINE.md §2.0`](../../docs/ENGINE.md#20-glossary-grill-prelude-mandatory-unless---no-grill). - §2.A or §2.B (preset-determined): build the root node from real evidence (Read files, Grep symbols, WebFetch references). The root must have the 5-8 fields the preset specifies, each with `file:line` or URL evidence.
Save the root to `<out>/tree.md` + `<out>/tree.json` before producing any framing branches.
### Step 3 — §3 framing pass (12 passes per node)
For each node (starting with root, then any high-verdict leaf in the next round):
Run §3.A through §3.L, each producing **at least 1** new child branch. See [`docs/framings.md`](../../docs/framings.md) for the full prompt per framing, including domain-specific examples per preset.
**Parallelize when fan-out ≥ 5** (always true for the root and hot leaves): dispatch the 12 framings across `Agent(Explore)` sub-agents per the mandatory protocol in [`docs/ENGINE.md` §8.1](../../docs/ENGINE.md#81-sub-agent-dispatch-mandatory-when-a-nodes-expected-fan-out--5). Running them sequentially at that fan-out is a defect. Deep marginal leaves (< 5 expected children) may run sequentially.
§3.X (if `--no-online` is off): per node, do 1 round of `WebSearch` + `WebFetch`. **The query set is preset-determined** (brainstorm/design → prior art + tooling; attack → critiques / errata; code-audit → CVEs / advisories) — see [`docs/framings.md`](../../docs/framings.md) §3.X.
### Step 4 — §4 per-branch 12-field derivation
For each branch produced in §3, fill the preset's 12 node-field schema. Field requirements live in [`docs/ENGINE.md §4`](../../docs/ENGINE.md#4-4-per-node-derivation-12-field-schema). Hard rules: - No field may contain `应该 / 大概 / probably / maybe / 也许` — the field is invalid and must be rewritten. - No field may contain `defer / future work / TODO / FIXME / 略 / details omitted / 待定 / NEEDS-MORE-INFO`-style placeholders — the node is forced to `INCOMPLETE_FORBIDDEN` and **must** be driven to completion before counting. - Numerical claims require a one-shot `python (sympy/numpy)` sanity check via `Bash` — output pasted into the field. - External references require `WebFetch` of the actual arXiv abs / DOI / spec page; `WebSearch` snippets are not sufficient.
Append the filled node to `tree.md` + `tree.json` immediately (incremental write — see §7 for crash-safety contract).
### Step 5 — §5 scoring and verdict
Score the node along the preset's 5 dimensions (each 0–3, integer). Sum = `score` (max 15). Map score → verdict via the preset's `verdict_enum` and the preset-specific rule (e.g. brainstorm: `score ≥ 11 ∧ no [NEEDS_VERIFICATION] → PROMISING`; attack: `score ≥ 11 ∧ artifact_defense empty → CONFIRMED`).
Sibling merging (§5.4): any two siblings with cosine similarity ≥ 0.85 on their idea / critique / option / finding statement → merge, keep the higher-scored one, tag the other `MERGED_INTO=<id>`.
### Step 6 — §6 convergence check
After every round, evaluate the 6 conditions in [`docs/ENGINE.md §6`](../../docs/ENGINE.md#6-6-convergence). All 6 must hold simultaneously to declare `CONVERGED`. If any user-specified `--width / --depth / --rounds` cap trips first, report the appropriate `*_CAP_REACHED` / `ROUNDS_EXHAUSTED` status, but **all leaves must be complete** before stopping.
If neither convergence nor a cap-trip, pick the highest-verdict leaf that hasn't been re-expanded yet, run §3–§5 on it, and loop.
### Step 7 — §7 final report
When termination is declared, write the preset's `output_artifacts` to `<out>/`. For all presets this includes: - `tree.md` — full tree, human-rea
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for tree, ready for a manual X post.
A practical pick for design or creative work: tree: Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes... 107 stars https://www.openagentskill.com/skills/skymanbp-tree?ref=x
Listing + install path for tree: https://www.openagentskill.com/skills/skymanbp-tree?ref=x Install: npx skills add skymanbp/cc-tree --skill tree
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to skymanbp but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/skymanbp-tree?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/skymanbp-tree?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/skymanbp-tree/audit)
[](https://www.openagentskill.com/skills/skymanbp-tree?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)skymanbp
@skymanbp
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsSandbox only
Install targets
Codex install prompt
Install the "tree" agent skill from https://github.com/skymanbp/cc-tree/tree/main/skills/tree. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes per node until stable convergence (no new high-verdict branches over the last 2 rounds + all 12 framings exercised + all leaves complete). Width × depth × rounds default to ∞; resource caps are opt-in. Hard ban on `defer / future-work / TODO / NEEDS-MORE-INFO` leaves — every leaf must be fully derived before counting. Use when 用户说 "brainstorm" / "attack" / "design exploration" / "code audit" / "explore options" / "find what's wrong" / "what should we build" / "tree of thoughts" / 想做穷尽的发散探索 / 想做多角度审查 / 想对一个工件 adversarial critique / 想做设计空间探索. Prefer the per-preset commands (`/cc-tree:brainstorm`, `/cc-tree:attack`, `/cc-tree:design`, `/cc-tree:code-audit`) when the use-case matches; call this skill directly with `--preset <name|path>` to override or supply a custom preset. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"skymanbp-tree","task":"Install tree","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add skymanbp/cc-tree --skill tree
Maintenance
fresh
3d since push
Risk
Needs review
Permission surface may require sandboxing
GitHub quality
107
67/100 Quality · 77/100 Trust
Coverage tags
Review notes
Permission surface may require sandboxing · Financial research output is not financial advice; require human review before any live investment decision
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
107 GitHub stars
Repo activity
107 stars, 0 forks
Maintenance
3d since push
License
MIT
Install
npx skills add skymanbp/cc-tree --skill tree
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add skymanbp/cc-tree --skill treeDo not use when
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20tree%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20tree%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/skymanbp-tree/install
Agent should check
Copy prompt
Task: Use tree in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20tree%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/skymanbp-tree/install
Install command: npx skills add skymanbp/cc-tree --skill tree
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/skymanbp-tree/install
LLM text format
/api/skills/skymanbp-tree/install?format=text
Find alternatives
/api/skills/search?q=tree&limit=3
Agent prompt
Use tree for this task. Review https://www.openagentskill.com/api/skills/skymanbp-tree/install, then install with: npx skills add skymanbp/cc-tree --skill treeRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/skymanbp-tree
LLM text
/api/registry/manifest/skymanbp-tree?format=text
Install alias
/api/registry/install/skymanbp-tree
Recommend
/api/registry/recommend?task=Use%20tree%20in%20an%20agent%20workflow&limit=3
Agent fit
Local desktop
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Local desktop
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO107 GitHub stars
Stars/forks activity
CHECK107 stars, 0 forks; issue activity unavailable in current metadata
Recent maintenance
PASS3d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Operate local tools
I need my agent to operate local files and desktop apps in a repeatable workflow.
Search private knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: tree description: Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes per node until stable convergence (no new high-verdict branches over the last 2 rounds + all 12 framings exercised + all leaves complete). Width × depth × rounds default to ∞; resource caps are opt-in. Hard ban on `defer / future-work / TODO / NEEDS-MORE-INFO` leaves — every leaf must be fully derived before counting. Use when 用户说 "brainstorm" / "attack" / "design exploration" / "code audit" / "explore options" / "find what's wrong" / "what should we build" / "tree of thoughts" / 想做穷尽的发散探索 / 想做多角度审查 / 想对一个工件 adversarial critique / 想做设计空间探索. Prefer the per-preset commands (`/cc-tree:brainstorm`, `/cc-tree:attack`, `/cc-tree:design`, `/cc-tree:code-audit`) when the use-case matches; call this skill directly with `--preset <name|path>` to override or supply a custom preset. disable-model-invocation: false argument-hint: "<root> --preset <name|path> [--lang <tag|auto>] [--width N|∞] [--depth N|∞] [--rounds N|conv] [--max-branches N|∞] [--out <dir>] [--glossary <path>] [--field <name|path>] [--seed-from <primary.md>] [--no-grill] [--no-online] [--min-frameworks N] [--min-novelty-ratio R] — `<root>` is a topic string, file path, problem statement, or design prompt; `--preset` is required (use `brainstorm` / `attack` / `design` / `code-audit` for shipped presets, or a path to your own .md)" ---
# tree — universal radial-tree exploration engine
> **What this skill is.** A single engine implementing recursive > radial-tree exploration (root → 12-framing expansion → per-node > 12-field derivation → score → recurse on high-verdict leaves → > terminate on **substantive convergence**). What varies between > use-cases (brainstorm vs critique vs design vs code-audit) is the > baseline recipe, node schema, scoring dimensions, and verdict > vocabulary — all parameterized via a **preset** file.
> **What this skill is NOT.** Not a one-shot LLM call that returns a > bulleted list. Not a chat interface — once `/cc-tree:tree` is > invoked, the engine runs to convergence without further prompts. > Not bundled with a model — pure prompt-engineering on top of Claude > Code's existing model setting.
The full engine specification lives in [`docs/ENGINE.md`](../../docs/ENGINE.md). This SKILL.md is a 7-step navigation guide; **Read `docs/ENGINE.md` before producing the first node** (the engine spec is what defines "valid" for everything you'll write).
---
## 1. Invocation
``` /cc-tree:tree <root> --preset <name|path> [flags] ```
**`<root>`** is preset-typed: - `brainstorm` preset → topic string, e.g. `"ways to detect dark-matter substructure"` - `attack` preset → file path (`.md` / `.tex` / etc.) or quoted argument-text - `design` preset → design-prompt string or `.md` file path - `code-audit` preset → file path or directory path
**`--preset`** is required: - Built-in: `brainstorm`, `attack`, `design`, `code-audit` (resolve to `presets/<name>.md` in this plugin) - Path: `./my-custom.md` (any .md file with the right frontmatter)
### Common flags (apply across presets)
| Flag | Default | Meaning | |---|---|---| | `--lang <tag\|auto>` | **en** | Output language for all localized prose (node statements, derivations, report narrative, warnings). Machine tokens — flag/command names, frontmatter & JSON keys, `root_kind` values, verdict labels, status tokens, filenames — always stay English. `<tag>` is a BCP-47-like code (`en`, `zh`, `zh-Hans`, `zh-Hant`, `fr-CA`); `zh` = Simplified Chinese, `zh-Hant` = Traditional. `auto` detects the dominant language of `<root>` and falls back to `en` for mixed / path-only / code-only input. Resolved **once before preset load**, recorded in run metadata (`language_request` / `output_language` / `language_source`), and never prompted mid-run. Full precedence, resume, and chain semantics: [`docs/ENGINE.md §1.0`](../../docs/ENGINE.md#10-output-language-resolution-and-schema-boundary). | | `--width N` | **∞** | Cap on final leaf count (the outer arc of the tree). `∞` / `inf` / unspecified all mean unlimited. | | `--depth N` | **∞** | Cap on tree depth from root. | | `--rounds N` | `conv` | Cap on expansion rounds. `conv` = no cap; terminate by §6 substantive convergence. | | `--max-branches N` | **∞** | Cap on new branches per node per round. **Floor is 12** because §3 requires all 12 framings to fire; this flag only raises the ceiling. | | `--out <dir>` | `tree-out/<UTCdate>__<slug>/` | Output directory. Per-preset commands override (e.g. `brainstorm-out/`). | | `--glossary <path>` | (preset-determined) | Path to a glossary / FACTS.md / glossary section in a dossier; used by §2.0 grill prelude. | | `--field <name\|path>` | (none) | Field profile for domain-aware reviewer weighting. `<name>` → `field-profiles/<name>.md` in this plugin; `<path>` → a literal file. Feeds §3.C / §3.D / §3.I / §3.J + the §3.X / §4 evidence bar. Missing profile → warn + continue (non-blocking). See [`docs/ENGINE.md` §2.2](../../docs/ENGINE.md#22-field-profile-optional---field-namepath). | | `--seed-from <primary.md>` | (none) | Seed the tree from a prior run's primary deliverable (`shortlist.md` / `options.md` / `confirmed.md`): each listed item enters as a depth-1 seed node and is re-expanded. The substrate for cross-preset chaining ([`docs/chaining.md`](../../docs/chaining.md)). Alias: `--from-prior`. | | `--no-grill` | off | Skip §2.0 glossary grill prelude. Marks root-node terms as `unverified`; §6 convergence adds a warning. | | `--no-online` | off | Disable `WebSearch` / `WebFetch`. Local + already-Read references only. | | `--min-frameworks N` | 12 | Minimum framing passes per node. **Floor is 12** (full §3.A–§3.L); flag exists for documentation, not relaxation. | | `--min-novelty-ratio R` | 0.15 | §6.1 condition 2 requires "last 2 rounds' high-verdict / total < R". |
> Presets and their command wrappers may document additional > preset-specific flags (e.g. `attack`'s > `--focus <section|claim|equation>`); a flag documented by the active > preset or its wrapper is not "unknown" (`docs/ENGINE.md` §1.3).
> Caps default to ∞ on purpose. The intended termination is §6 > substantive convergence — see [`docs/ENGINE.md §6`](../../docs/ENGINE.md#6-6-convergence). > Caps are escape valves for quick exploration; when one trips, the > engine still drives every in-flight node to a complete state before > reporting `WIDTH_CAP_REACHED` / `DEPTH_CAP_REACHED` / > `ROUNDS_EXHAUSTED`.
---
## 2. Execution flow
> **Required Reads at session start** (before producing the first node): > 1. The preset file (`presets/<name>.md` or `--preset <path>`) — full file. > 2. [`docs/ENGINE.md`](../../docs/ENGINE.md) — full file. This is the contract. > 3. [`docs/framings.md`](../../docs/framings.md) — the 12 framings with per-preset > examples. > 4. If `--glossary <path>`: Read that glossary file in full.
### Step 1 — Preset load
Open the preset file. Extract from its YAML frontmatter: - `name`, `description`, `use-when` (informational) - `root_kind` — `topic | artifact | code | design-prompt` - `subject_label` — what each tree node is called (`idea`, `critique`, `option`, `audit-finding`, …) - `verdict_enum` — 4-tuple: `advances / kept / pruned / blocked` - `convergence_metric` — which verdict *role* counts toward the §6.1 condition-2 ratio. It must be one of the four `verdict_enum` role keys verbatim (`advances` / `kept` / `pruned` / `blocked`); alias spellings like `novelty_ratio` are rejected by the validator. All four shipped presets use `advances` ([`docs/presets.md`](../../docs/presets.md)) - `score_dims` — list of 5 scoring dimensions (key + name + desc) - `node_schema` — list of 12 node-field names - `output_artifacts` — file names for the per-verdict final reports
The preset body (below frontmatter) supplies: - §2 baseline recipe (what to Read / Grep / WebFetch to build the root) - Optional per-framing examples (§3.A–§3.L flavored for this preset) - Optional anti-pattern list specific to this preset
### Step 2 — §2 baseline
Follow the preset's baseline recipe. For all presets this includes: - §2.0 (unless `--no-grill`): glossary-grill prelude. Lock root-node noun-phrases to the glossary if one was supplied; surface MISSING / AMBIGUOUS / CONFLICT one question at a time per [`docs/ENGINE.md §2.0`](../../docs/ENGINE.md#20-glossary-grill-prelude-mandatory-unless---no-grill). - §2.A or §2.B (preset-determined): build the root node from real evidence (Read files, Grep symbols, WebFetch references). The root must have the 5-8 fields the preset specifies, each with `file:line` or URL evidence.
Save the root to `<out>/tree.md` + `<out>/tree.json` before producing any framing branches.
### Step 3 — §3 framing pass (12 passes per node)
For each node (starting with root, then any high-verdict leaf in the next round):
Run §3.A through §3.L, each producing **at least 1** new child branch. See [`docs/framings.md`](../../docs/framings.md) for the full prompt per framing, including domain-specific examples per preset.
**Parallelize when fan-out ≥ 5** (always true for the root and hot leaves): dispatch the 12 framings across `Agent(Explore)` sub-agents per the mandatory protocol in [`docs/ENGINE.md` §8.1](../../docs/ENGINE.md#81-sub-agent-dispatch-mandatory-when-a-nodes-expected-fan-out--5). Running them sequentially at that fan-out is a defect. Deep marginal leaves (< 5 expected children) may run sequentially.
§3.X (if `--no-online` is off): per node, do 1 round of `WebSearch` + `WebFetch`. **The query set is preset-determined** (brainstorm/design → prior art + tooling; attack → critiques / errata; code-audit → CVEs / advisories) — see [`docs/framings.md`](../../docs/framings.md) §3.X.
### Step 4 — §4 per-branch 12-field derivation
For each branch produced in §3, fill the preset's 12 node-field schema. Field requirements live in [`docs/ENGINE.md §4`](../../docs/ENGINE.md#4-4-per-node-derivation-12-field-schema). Hard rules: - No field may contain `应该 / 大概 / probably / maybe / 也许` — the field is invalid and must be rewritten. - No field may contain `defer / future work / TODO / FIXME / 略 / details omitted / 待定 / NEEDS-MORE-INFO`-style placeholders — the node is forced to `INCOMPLETE_FORBIDDEN` and **must** be driven to completion before counting. - Numerical claims require a one-shot `python (sympy/numpy)` sanity check via `Bash` — output pasted into the field. - External references require `WebFetch` of the actual arXiv abs / DOI / spec page; `WebSearch` snippets are not sufficient.
Append the filled node to `tree.md` + `tree.json` immediately (incremental write — see §7 for crash-safety contract).
### Step 5 — §5 scoring and verdict
Score the node along the preset's 5 dimensions (each 0–3, integer). Sum = `score` (max 15). Map score → verdict via the preset's `verdict_enum` and the preset-specific rule (e.g. brainstorm: `score ≥ 11 ∧ no [NEEDS_VERIFICATION] → PROMISING`; attack: `score ≥ 11 ∧ artifact_defense empty → CONFIRMED`).
Sibling merging (§5.4): any two siblings with cosine similarity ≥ 0.85 on their idea / critique / option / finding statement → merge, keep the higher-scored one, tag the other `MERGED_INTO=<id>`.
### Step 6 — §6 convergence check
After every round, evaluate the 6 conditions in [`docs/ENGINE.md §6`](../../docs/ENGINE.md#6-6-convergence). All 6 must hold simultaneously to declare `CONVERGED`. If any user-specified `--width / --depth / --rounds` cap trips first, report the appropriate `*_CAP_REACHED` / `ROUNDS_EXHAUSTED` status, but **all leaves must be complete** before stopping.
If neither convergence nor a cap-trip, pick the highest-verdict leaf that hasn't been re-expanded yet, run §3–§5 on it, and loop.
### Step 7 — §7 final report
When termination is declared, write the preset's `output_artifacts` to `<out>/`. For all presets this includes: - `tree.md` — full tree, human-rea
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for tree, ready for a manual X post.
A practical pick for design or creative work: tree: Universal radial-tree exploration engine. Loads a preset, builds a §2 baseline, then recursively applies 12 framing passes... 107 stars https://www.openagentskill.com/skills/skymanbp-tree?ref=x
Listing + install path for tree: https://www.openagentskill.com/skills/skymanbp-tree?ref=x Install: npx skills add skymanbp/cc-tree --skill tree
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to skymanbp but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/skymanbp-tree?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/skymanbp-tree?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/skymanbp-tree/audit)
[](https://www.openagentskill.com/skills/skymanbp-tree?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)skymanbp
@skymanbp
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsPermission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness