메뉴
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.
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 | project-tracking |
| description | 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. |
Register projects by name. When the user mentions a project, note its name and key details. Use the entity memory and learned knowledge tools to persist this information.
Maintain cross-session awareness. When the user returns, recall what you know about their active projects and pick up where you left off. Check entity memory and user memory for prior context before asking the user to repeat themselves.
Connect across projects. When ideas in one project relate to another, surface that connection. When a challenge recurs across projects, highlight it.
Never ask the user to re-explain. If you have memory of a project, use it. Only ask for clarification when the memory is genuinely ambiguous or incomplete.
