agent-team-foundation/first-tree-write
skills/first-tree-write/SKILL.md
Write Context Tree updates from explicit source material — code PRs, design docs, meeting notes, raw text. Use when the user gives you a concrete source and wants the right durable tree change drafted, linked, and reviewed. This skill is source-driven and targeted; use `first-tree-sync` instead for broad drift audits with no specific source.
$ install --global
skillsauthnpx skillsauth add agent-team-foundation/first-tree first-tree-writeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 4, 2026, 2:05 AM59.8s6 files scanned
SKILL.md
- name:
- first-tree-write
- version:
- 0.4.0-alpha.1
- first-tree:
- >=0.4.0 <0.5.0
- description:
- Write Context Tree updates from explicit source material — code PRs, design docs, meeting notes, raw text. Use when the user gives you a concrete source and wants the right durable tree change drafted, linked, and reviewed. This skill is source-driven and targeted; use `first-tree-sync` instead for broad drift audits with no specific source.
First Tree Write
Read these first:
../first-tree/SKILL.md../first-tree/references/anti-patterns.md../first-tree/references/maintenance.md
What This Skill Does
Take one specific source — a PR, a doc, a note — and produce zero, one, or a small set of tree changes that capture what's durable and decision- relevant. The output is a tree-repo PR linked to the source.
When To Use This Skill
| Use this skill | Use a different skill |
| ------------------------------------------------------------ | ----------------------------------------------------------------------------- |
| User pastes a PR link and says "reflect this in the tree" | User asks "is the tree up to date?" → first-tree-sync |
| User pastes a meeting note about a decision | Repo is unbound → first-tree-onboarding first |
| User pastes raw text and asks for the tree implication | A GitHub notification needs only a label / comment → first-tree-github-scan |
| GitHub Scan agent classifies a notification as route=write | Audit drift since a release → first-tree-sync |
The Default Stance
Default to not writing. The tree compresses expensive context; a node nobody reads is worse than a missing node. If the source does not clearly establish a decision, constraint, ownership change, or cross-domain relationship, write nothing and tell the user why.
How To Run
| Phase | Reference | | ----------------------------- | -------------------------------------------------------- | | Decide what is tree-worthy | references/what-belongs.md | | Draft the update | references/workflow.md | | Shape the tree node | references/node-shape.md | | Decide between write and sync | references/boundary.md |
The CLI surface this skill uses today:
first-tree tree inspect --json— confirm the bindingfirst-tree tree verify --tree-path <path>— gate the final commitgh pr create— open the tree-repo PR
There is no first-tree tree write-node or tree open-tree-pr command
yet — write builds the file edits + commit + PR with gh and standard
git.
Hard Rules
- Source-driven only. No source means no write task. Send the user
to
first-tree-syncif they want broad audit. - Default to not writing. Apply both decision and durability tests
before drafting anything (see
references/what-belongs.md). - No diffs in the tree. Capture decisions and rationale, not code detail. The diff lives in the source PR.
- Smallest correct edit. Bias hard toward editing existing nodes. Adding a new domain is a high-bar move.
- Verify before commit.
first-tree tree verifymust exit 0 before opening the tree PR. - Link the source. Every tree change must link back to the PR / doc / note that motivated it.
- Do not chain into other skills. Finish the write task; suggest follow-ups in the PR body if you noticed adjacent drift.
References
- what-belongs.md — judgment filter; the decision/durability tests and worked examples
- workflow.md — five-step recipe (read source, identify tree-worthy content, choose smallest edit, draft, verify and link)
- node-shape.md — frontmatter rules, body structure, and a worked example
- boundary.md — write vs sync decision table and hand-off mechanics
Related Skills
agent-team-foundation/first-tree
tools
VerifiedTrustedCommunity
Canonical whitepaper and routing skill for First Tree. Explains what belongs in a Context Tree, how source or workspace roots, tree repos, and bindings relate, and how the current `first-tree tree` and `first-tree github scan` surfaces fit together. Use when you need shared First Tree concepts, need to choose between onboarding, sync, write, or GitHub notification workflows, or need the high-level CLI map before acting.
44SKILL.mdUpdated Apr 25, 2026
agent-team-foundation/first-tree-onboarding
tools
VerifiedTrustedCommunity
One-shot onboarding command for First Tree. Drives a repo or workspace from "no first-tree" all the way to "tree bound, real content drafted, daemon running, agent templates confirmed" — end to end, in one skill invocation. Trigger this skill when the user invokes `/first-tree-onboarding`, says "onboard this repo to first-tree", "set up first-tree here", "complete first-tree onboarding", or runs first-tree against an unbound repo or workspace. Also trigger when re-running on an already-bound repo to refresh skills, draft missing content, or reverify the daemon. Use this skill instead of running `first-tree tree init` from raw memory; it owns role-by-role branching, the initial-content drafting phase the CLI does NOT do, and the final doctor checks.
39SKILL.mdUpdated May 2, 2026
agent-team-foundation/first-tree-sync
development
VerifiedTrustedCommunity
Audit and repair drift between merged code and the Context Tree in both directions — tree→code (does code still support tree facts?) and code→tree (does the tree register everything code now contains?). Use when the tree may be stale, wrong, outdated, or missing coverage for recent code changes; after a large merge; before release; on a freshly onboarded tree; or when a GitHub notification was routed `route=sync`. Sync owns broad drift discovery, structural skeleton repair, and substantive write hand-off across one tree. Use `first-tree-write` instead when the user already gave you a specific PR / doc / note to write into the tree.
33SKILL.mdUpdated May 2, 2026
agent-team-foundation/github-scan
tools
VerifiedTrustedCommunity
Operate the `first-tree github scan` CLI — the GitHub notification daemon and inbox runtime. Use whenever you need to run, start, stop, inspect, poll, or debug github-scan; view or respond to GitHub-triggered work from the terminal; or wire up the github-scan statusline hook.
32SKILL.mdUpdated May 7, 2026