菜单
Discover and vet reusable skill opportunities from the user's Glean work patterns. Use when the user asks "what should I automate", "find skill opportunities", or wants to turn recurring work into skills. For authoring a known skill in Codex, hand off to the built-in skill-creator.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Synthesize the user's own work activity, priorities, and recent context using Glean — use when the user asks about their recent work, what they accomplished, what is urgent, what needs their attention, or wants help with status updates, 1:1 prep, or weekly summaries. Trigger phrases include what have I been working on, what did I do last week, what should I focus on, summarize my week, help me with my status update, what's blocking me, morning briefing, what happened while I was out. Do not use for general enterprise queries (use the using-glean skill), for someone else's activity, or for project-status questions where the user is not the subject (use a project-awareness skill).
Use Glean MCP tools to answer questions about company documents, internal wikis, policies, RFCs, design docs, people, teams, meetings, decisions, action items, email, calendar events, internal code, and the user's own work activity. Reach for this whenever the answer lives in enterprise systems rather than the local codebase or public web. Trigger phrases include "find the doc about", "what's our policy on", "where is the spec for", "who works on", "who owns", "find someone who knows", "what was decided in the meeting", "action items from", "search my email", "what did I work on last week", and "find the implementation in our repos". Don't use it for questions answerable from the local working directory, the public web, or generic programming knowledge.
Help the user connect a Glean MCP server so the Glean skills have tools to call — use when setting up Glean for the first time, adding another Glean server, checking whether Glean is connected, or troubleshooting missing Glean tools. Trigger phrases include "set up Glean", "connect Glean", "configure Glean MCP", "add a Glean server", "is Glean connected", "check Glean status", "Glean isn't working", "no Glean tools", "the Glean tools aren't showing up", "I installed the Glean plugin but nothing happens". Don't use it for actual enterprise queries once connected (use the using-glean skill); this skill only sets up and verifies the connection.
Generate a comprehensive handoff document so someone new can take over a project — current state, key people, essential knowledge, open items, and a first-30-days plan. Use when the user is handing off a project (trigger phrases include "generate a handoff", "hand off this project", "create a handoff doc", "I'm going on PTO / leaving / changing teams and need to document", "help someone take over") rather than a quick status read (use project-awareness for that).
Guide the user through authoring a new agent skill — when a skill is worth creating, the SKILL.md format, progressive disclosure, and common pitfalls. Also covers discovering skill opportunities from the user's work patterns and generating a SKILL.md from a description. Trigger phrases include "create a skill", "write a skill", "make a skill", "new skill", "SKILL.md format", "how do skills work", "skill best practices", "convert this workflow into a skill", "what should I automate", and "find skill opportunities". Don't use it for invoking existing skills — only when authoring a new one or understanding the skill format.
| name | skill-creation-guide |
| description | Discover and vet reusable skill opportunities from the user's Glean work patterns. Use when the user asks "what should I automate", "find skill opportunities", or wants to turn recurring work into skills. For authoring a known skill in Codex, hand off to the built-in skill-creator. |
Help the user identify valuable agent-skill opportunities from Glean context.
Vet candidates carefully, then hand actual authoring to Codex's built-in
$skill-creator.
Not every idea makes a good skill. Evaluate before creating:
Recurrence — Will this be used repeatedly?
Automation — Can it actually be automated?
Value — Is the cumulative time saved significant?
Duplication — Does it already exist?
Don't create skills for one-time events, tasks that differ fundamentally each time, sub-30-second manual tasks, or things the user will forget exist.
When the user asks what they should automate, analyze their work patterns first.
Requires the Glean MCP tools. If they aren't visible, the user hasn't connected a Glean MCP server — point them at the connect-glean skill.
memory (roles, responsibilities, active
projects), user_activity (past ~2 weeks), and search for process docs
("runbook OR checklist OR process owner:me").See using-glean/reference/ for the param shape of memory, user_activity,
and search.
When the user selects a candidate or already has a specific skill in mind:
$skill-creator.$skill-creator determine the final structure, files, and installation
location. Do not duplicate its generation workflow here.$skill-creator — authors and validates the selected skill for Codex.