$ loading_
Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "creating-skills" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/FluidFramework/main/.agency/plugins/nori/skills/creating-skills/SKILL.md 2. 保存为 ~/.claude/skills/creating-skills/SKILL.md 3. 装好后重载技能，告诉我可以用了
This skill guides you through creating custom skills that persist across sessions. Skills are stored in profile directories and can include markdown instructions, checklists, and optional bundled scripts.
Every skill must start with a required checklist block:
<required>
*CRITICAL* Add the following steps to your Todo list using TodoWrite:
1. <step 1>
2. <step 2>
...
</required>
This is the most important part of a skill.
Each step may have guidelines underneath. For example:
1. Create a directory.
Use `mkdir foo/bar`
2. Make a file.
...
Skills may be bundled with scripts. Scripts are simple code cli tools that do various things deterministically.
Any scripts you write should be entirely self contained. Ask the user which language they prefer.
The scripts should be callable from the Bash tool.
The script should be stored in the same place as the skill. Add a section to the SKILL.md on how to use the script. If the script is required to be called, add that instruction to the <required> block.
Document which tools are necessary for the skill.
The SKILL should explicitly encourage writing code. The agent should be told to write code to call a tool any time the agent needs to call any tools more than once. The agent should write code instead of calling tools itself.
Steps that reference tools and APIs should inline them in the step by step process.
<good-example> - Write a python script that uses the slack api to pull my unread messages. The script should write my messages to a folder, /home/foobar/daily-analysis/<DD-MM-YYYY>/slack - Write a python script that uses the gmail api to pull my inbox. The script should write my emails to a folder, /home/foobar/daily-analysis/<DD-MM-YYYY>/email - Write a python script to identify the most urgent messages that I need to respond to. <system-reminder> Auth credentials can be found at /home/foobar/authentication/auth.txt </good-example> <bad-example> **Tools**: Slack, Gmail API - Summarize my messages by looking through common surfaces that I may use for messages. </bad-example> <good-example> Read https://raw.githubusercontent.com/tilework-tech/nori-skillsets/96012bcfcd9482b248debed7b9a7fc7c345f76e1/src/cli/features/claude-code/profiles/config/amol/skills/finishing-a-development-branch/SKILL.md </good-example> <good-example> Read https://raw.githubusercontent.com/tilework-tech/nori-skillsets/96012bcfcd9482b248debed7b9a7fc7c345f76e1/src/cli/features/claude-code/profiles/config/amol/skills/webapp-testing/SKILL.md </good-example>Use this skill for any Kusto query or telemetry investigation specifically related to Fluid Framework or its partners. Triggers include: writing or running a Kusto query against the Office Fluid database, investigating Fluid Framework telemetry or error rates, querying Office_Fluid_FluidRuntime_* tables, looking up a Fluid session by Session_Id or docId, investigating a Fluid-related error in Loop or Whiteboard telemetry, monitoring an FF bump or partner ring deployment, checking Fluid render reliability or Scriptor errors, or when the user mentions Fluid-specific tables (Office_Fluid_FluidRuntime_*, OwhLoads, HostTracker, Scriptor) or Fluid-specific error types (dataCorruptionError, dataProcessingError, DeltaConnectionFailureToConnect, ICE, ACE). Do NOT trigger for general Kusto questions that are not related to Fluid Framework.
IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
Use when implementing user interfaces or user experiences - guides through exploration of design variations, frontend setup, iteration, and proper integration
Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.
Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
Generate the OCE shift status dashboard. Triggers on: 'generate shift dashboard', 'show dashboard', 'shift status', 'status dashboard', 'what's going on', or any request for a NON-SPECIFIC overview of current OCE status (incidents, pipelines, errors).