first-tree-welcome

Solid

Use for a First Tree onboarding first chat, especially natural opening messages like "welcome aboard", "Please help me get started with First Tree", or "Please help me get settled into this team on First Tree." Also covers the production-scan fix first chat ("fix the launch blockers found by my production readiness scan"). Do not use for dedicated tree setup chats, ordinary chats, PR/MR reviews, repo scans, tree writes, or maintenance.

AI & Automation 142 stars 37 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 82/100

Stars 20%
72
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# First Tree Welcome ## Scope Use this skill only when the chat is clearly the onboarding first chat created by First Tree, including natural messages such as "welcome aboard", "Please help me get started with First Tree", or "Please help me get settled into this team on First Tree." Do not use it for ordinary chats, PR/MR reviews, repo scans, tree writes, or maintenance work. Two look-alikes that are NOT this launcher, and one that routes by shape: - **A dedicated tree-build / single-task chat** (you were placed in it, or it IS one) — run that task's own skill (`first-tree-seed` to build/seed a tree, `first-tree-read` / `first-tree-write` as appropriate), not this launcher flow. - **A repo-scan chat** — it can open with the same "welcome aboard" line but then asks for a repository scan or readiness report; run its own bound scan skill. - **A production-scan FIX chat** — the opening message references an already-completed scan ("fix the launch blockers found by my production readiness scan") with a `Repository:` line, plus a `Machine-readable findings: https://report.first-tree.ai/<key>.json` line when the report key survived the handoff. Nothing needs re-scanning — never look for a scan skill. This is the launcher for a pre-selected fix: once a readable findings source exists, route by blocker count — several eligible blockers become their own fix chats, a single one is just fixed in place (see "Production-scan fix handoff" below). The onboarding gr...

Details

Author
agent-team-foundation
Repository
agent-team-foundation/first-tree
Created
5 months ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

first-tree-seed

Bootstrap a team's Context Tree from readable source repos — for an onboarding "build / set up the Context Tree" task on a tree that has no domain structure yet: either no tree exists (creates and binds it) or a bound-but-empty tree (fills it). Supports clean explicit-Team invocation without a Workspace manifest, managed briefing, or prior setup-chat transcript, while preserving managed-workspace compatibility. Proposes an initial top-level + second-level domain structure for approval, then drafts initial leaf content — each as a reviewable PR/MR. Refuses unrelated re-seeding once the tree has domain structure and recovers Phase 2 from durable merged Tree state plus the same explicit sources.

142 Updated today
agent-team-foundation
AI & Automation Solid

first-tree-read

Read the applicable Context Tree before acting. In BYO sessions, route only among locally authorized Teams by reading each exact root SCOPE.md before selecting one task snapshot; in managed workspaces, use the bound Tree. Do not use for a Context Tree PR/MR review or an explicit broad audit of stored tree content.

142 Updated today
agent-team-foundation
AI & Automation Solid

first-tree-write

Source-driven Context Tree write workflow for managed and BYO consumers. BYO always requires the exact SCOPE-routed read snapshot and a new user confirmation of the precise Team/source/targets/mutation plan before any Tree mutation. If no source artifact is available, there is no write task.

142 Updated today
agent-team-foundation