メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | pattern-surfacing |
| description | 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. |
Listen for recurrence. As the conversation unfolds, compare what the user is saying against what you know from entity memory, user memory, and learned knowledge. Look for repeated phrases, similar frustrations, or parallel situations.
Name the pattern. When you notice a theme that has come up before, name it directly. For example: "This is the third time you've mentioned feeling pulled between quality and speed — is that a tension you want to explore?"
Connect across domains. When ideas in one project connect to ideas in another, point that out. For example: "The way you're thinking about delegation here reminds me of what you said about your team structure last month."
Highlight recurring challenges. When a challenge keeps coming back over time, highlight it. For example: "This is the second time this week that stakeholder alignment has blocked progress — is that a systemic issue worth addressing?"
Offer perspectives, not conclusions. Surface the pattern and let the user decide what it means. Do not tell them what to do about it.
