sandbox-branch-land
Create a dedicated git branch (and optional PR) for any work that lived only in a sandbox, zip, or agent session and never reached the repo. Use when the founder says sandboxed, unshipped, uncommitted, or "land the sandbox".
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- sandbox-branch-land
- description
- Create a dedicated git branch (and optional PR) for any work that lived only in a sandbox, zip, or agent session and never reached the repo. Use when the founder says sandboxed, unshipped, uncommitted, or "land the sandbox".
03 SKILL.md 正文
Sandbox Branch Land
Problem
Work often exists only in:
- Agent sandbox / container artifacts
- Zip uploads (e.g. TheCopy-ops, Grok session zips)
- Local paths never pushed
- PR descriptions that point at artifacts outside git
That work is invisible to main and dies with the session unless branched.
When
- Founder says: sandboxed, never committed, unshipped, land the zip, recover session work
- A PR or plan references files that are not in the tree
- After any long session that produced code outside a feature branch
Procedure
- Inventory — list paths/artifacts that exist outside the repo (artifact folders, zips, prior session notes). Do not invent files.
- Branch —
grok/sandbox-land-YYYY-MM-DDoragent/sandbox-<topic>-YYYY-MM-DDfrom currentmain(or the branch the founder names). - Prefix — land under a deliberate root (
sandbox-ops/,artifacts/, or topic folder). Never flatten onto repo root if that would overwrite Queen README or package manifests (lesson from PR #190). - Commit — real content only; note in commit body what remains zip-only if not fully expanded.
- PR — open for founder review; mark draft if partial. Body must say: what is in git vs still only in the zip.
- Do not merge unless founder explicitly directs (standing hive rule).
Anti-patterns
- Claiming "all 183 files landed" when only a subset is expanded
- Overwriting root
README.mdorworker/src/index.jsfrom an unrelated sandbox - Skipping the inventory step and dumping an entire zip blindly
Relation to plan-sync
After the branch exists, run plan-sync so PLAN_LOG / full-plan name the land attempt and what is still pending.
04 同仓库更多 Skills
preamble-gate
Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent/subagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI/triggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log/diff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.
visionary-recommender
暂无简介
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.
research
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.