Git
v1.0.0

First Tree

by @agent-team-foundation0 pulls
URLopenbooklet.com/s/first-tree
Pinnedopenbooklet.com/s/first-tree@1.0.0
APIGET /api/v1/skills/first-tree

This is the entry-point skill for the `first-tree` toolkit. It teaches:

5 skills from this repoagent-team-foundation/first-tree
First Treeviewing
Breeze — Operational Skillskills/breeze/SKILL.md

This skill is the operational handbook for the `breeze` product. If you have not yet loaded the `first-tree` entry-point skill, load that first — it explains the toolkit layout and how the four skills relate. This skill covers *how* to drive the `first-tree breeze` CLI.

first-tree-github-scanskills/first-tree-github-scan/SKILL.md

Agent skill for handling a single GitHub notification inside the First Tree github-scan daemon path. Use when an agent needs to decide how to tag, comment on, escalate, or hand off a PR, issue, review request, mention, or CI event, and when it needs to decide whether to involve a human or trigger `first-tree-sync` or `first-tree-write`. This is not the human CLI operations guide for the daemon.

first-tree-onboardingskills/first-tree-onboarding/SKILL.md

Onboard a repo or workspace to First Tree using the current CLI surface and the proposal-aligned five-step setup flow. Use when a repo is unbound, when a workspace needs a shared tree, when you need to choose between creating a new tree and binding an existing one, or when you need to install or start the GitHub scan daemon and prepare agent templates.

first-tree-writeskills/first-tree-write/SKILL.md

Write Context Tree updates from explicit source material such as code PRs, design docs, meeting notes, or raw text. Use when the user gives you concrete inputs and wants the right durable tree changes drafted, linked, and reviewed. This skill is source-driven and targeted; use `first-tree-sync` instead for broad drift audits.

Auto-indexed from agent-team-foundation/first-tree

Are you the author? Claim this skill to take ownership and manage it.

Related Skills

@openbooklet

graceful-error-recovery

Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.

1.1K0
@openbooklet

audience-aware-communication

Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.

1.1K0
@openbooklet

Refactoring Expert

Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.

600
@openbooklet

Research Expert

Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.

600
@openbooklet

clarify-ambiguous-requests

Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.

1.1K0
@openbooklet

structured-step-by-step-reasoning

Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.

1.1K0