zeroteam-one

Strategic guidance for the ask_user tool (UserFeedbackTools) — when to pause and ask the user structured questions, how to design options, anti-patterns to avoid, and how to behave after the run resumes. Load this skill before calling ask_user whenever you need to clarify intent, resolve a trade-off, or collect a preference that genuinely shapes your next action.

Execute an AgentOS implementation plan to completion — create/edit files, register agents, add evals, validate, smoke-test, update AGENTS.md, write a report. Use when a plan exists and you want it built. Covers Agno conventions and AGENTS.md update mapping.

Plan implementations of new agents, teams, workflows, and capabilities for AgentOS (Agno + Postgres + pgvector). Use when architecting or scoping before coding. Covers agent shape, DB isolation, guardrails, evals, promotion.

Governing delivery rules, energy calibration, pattern portfolio, self-check protocol, and priority matrix for the ThinkingPartner behaviours. Load this skill whenever any behaviour trigger fires — it provides the rules that govern every response, plus the two always-on behaviours (Energy Calibration, Pattern Portfolio). Other ThinkingPartner skills (contextual, expansions, examples) load alongside this one.

Delegate calendar tasks to the CalendarAgent via AgentOS MCP. The thinking partner does not have direct calendar tools — it calls the calendar agent when the user needs to view, search, create, update, or delete events.

Interact with Google Drive scoped to the collab001 project folder. List, search, read, upload, and download files — all operations are restricted to the collab001 folder. Uses a service account that has been granted access to the folder.

Generate ideal (best-case) outcomes for a stakeholder group — the ceiling when everything has gone perfectly to plan, not the floor of what's acceptable. Use this skill when the user asks for ideal outcomes, best-case outcomes, or the best-case scenario for a stakeholder group, or when generating outcomes and the user wants the ceiling not the floor. Also use when the user has asked for ideal outcomes and the response is drifting toward acceptable or realistic outcomes.

Surface patterns, recurring themes, and connections across the user's thinking. Identify when ideas in one area relate to another, and highlight challenges that keep coming back.

Track projects by name across sessions. Remember active projects, recall context when the user returns, and maintain cross-session project awareness so the user never has to re-explain a project.

Specifications for the four contextual ThinkingPartner behaviours that provide framing rather than new territory — Assumption Excavation, Version Awareness, Decision Archaeology, Blind Spot Mirroring. Load this skill when a contextual behaviour trigger fires (the question rests on an assumption that contradicts a stored decision, references a stale entity version, revisits a topic with stored decision history, or contains an unstated limiting assumption). These behaviours MAY co-occur with one expansion. Load thinking-partner-core alongside this skill.

Three worked examples demonstrating the ThinkingPartner behaviours in action — low-energy (suppress expansions), high-energy (spark + contrast), and co-occurrence (archaeology + one expansion). Load this skill when calibrating response style, seeing how a specific behaviour should be delivered, or checking how the delivery rules and energy calibration interact in practice.

Specifications for the six expansion ThinkingPartner behaviours that add new territory — Premature Convergence Prevention, Connection Surfacing, Contrast Seeding, Explorer Mode, Spark Timing, Diminishing Returns Detection. Load this skill when an expansion behaviour trigger fires (the question narrows before the decision space is explored, touches a concept with cross-domain links, optimises for one pole of a tension, or the user has been in director mode for 5+ turns). MUST select at most one expansion per response. Load thinking-partner-core alongside this skill.

Design and implement Agent Skills following best practices for VS Code and any Agent Skills-compatible agent. Use this skill when the user wants to create a new skill, improve an existing skill, review a skill for quality, or learn skill authoring best practices. Covers scoping decisions, instruction patterns, progressive disclosure, description optimization, and evaluation workflows.