- 📁 csharp/
- 📁 curl/
- 📁 go/
- 📄 SKILL.md
Claude-Code
Restored placeholder content.
Restored placeholder content.
Creates a new CLI command following the Commander.js pattern in src/commands/. Handles command registration in src/cli.ts, telemetry tracking via tracked() wrapper, and option parsing. Use when user says 'add command', 'new CLI command', 'create subcommand', or asks to add files to src/commands/. Do NOT use for modifying existing commands or refactoring command logic.
This skill should be used when the user asks to "test a saas cross-repo feature", "deploy a feature branch to staging", "test SDK against OH Cloud branch", "e2e test a cloud workspace feature", "test secrets saas inheritance", or when changes span the SDK and OpenHands enterprise and need end-to-end validation against a staging deployment.
Browser automation CLI for direct website interaction. Use when the user needs to open URLs, click buttons, fill forms, take screenshots, log in, or test web apps. NOT for web search.
Create, build, deploy, and localize declarative agents for M365 Copilot and Teams. USE THIS SKILL for ANY task involving a declarative agent — including localization, scaffolding, editing manifests, adding capabilities, and deploying. Localization requires tokenized manifests and language files that only this skill knows how to produce. Trigger phrases include "create agent", "create a declarative agent", "new declarative agent", "scaffold an agent", "new agent project", "make a copilot agent", "add a capability", "add a plugin", "configure my agent", "deploy my agent", "fix my agent manifest", "edit my agent", "modify my agent", "localize this agent", "localize my agent", "add localization", "translate my agent", "add a language", "multi-language agent", "add an API plugin", "add an MCP plugin", "add OAuth to my plugin", "add logo to my agent" --- # M365 Agent Developer ## ⛔ Workspace Check — MANDATORY FIRST STEP **Before doing ANYTHING, check the workspace files to fingerprint the project:** 1. Run `npx -y --package @microsoft/m365agentstoolkit-cli atk --version` to confirm ATK CLI is installed. If not found → **Stop.** Tell the user to install ATK. 2. Check for `m365agents.yml` or `teamsApp.yml` at the project root. 3. Check for `appPackage/declarativeAgent.json`. 4. Check for non-agent indicators (`package.json` with express/react/next, `src/index.js`, `app.py`, etc.) **Then follow the decision gate:** | Condition | Gate | Action | |-----------|------|--------| | Non-agent project files, no `appPackage/` | **Reject** | Text-only response. No files, no commands. | | No manifest, user wants to edit/deploy | **Reject** | Text-only response. Explain manifest is missing. | | No manifest, user wants new project | **Scaffold** | → [Scaffolding Workflow](references/scaffolding-workflow.md) | | Manifest exists with errors | **Fix** | Detect → Inform → Ask (see below). Do NOT deploy. | | Valid agent project | **Edit** | → [Editing Workflow](references/editing-workflow.md)
Author, read, debug, and modify Claude Code hooks — the user-defined shell commands, HTTP endpoints, or LLM prompts that run automatically at lifecycle events like PreToolUse, PostToolUse, Stop, SessionStart, UserPromptSubmit, and many more. Use this skill whenever the user mentions "hooks", "Claude Code hooks", a `.claude/settings.json` hooks block, auto-formatting on edit, blocking dangerous commands, Stop/PreToolUse/PostToolUse/SessionStart/etc., hook input JSON, `hookSpecificOutput`, `permissionDecision`, exit code 2 behavior, `CLAUDE_PROJECT_DIR` in hook scripts, or wants to guard, observe, or automate anything at a specific point in Claude Code's execution. Also use when the user asks to write a script that "runs before/after" a tool call, runs "when Claude finishes", or wants deterministic guardrails the model can't ignore.
AI Instructions Diagnostics | Supported agents: Claude | Codex | Copilot | Cursor | Gemini
Submit a bug report for the Plain framework. Use when the user wants to report a bug, error, or unexpected behavior. Collects context and creates a GitHub issue.
Verifies truthfulness, accuracy, and link integrity of content before publishing. Catches fabricated statistics, dead URLs, misattributed sources, and company claims that contradict the brand DNA.
>-
Navigates the agent to a target appliance (microwave, stove, fridge, or sinkbasin) needed for object processing. Use when you are holding an object that needs heating, cooling, or cleaning and must move to the correct appliance station. Identifies the required appliance from the task context and executes the movement action.
Full Sentry SDK setup for Mini Programs — error monitoring, tracing, offline cache, source maps. Supports WeChat, Alipay, ByteDance, Baidu, QQ, DingTalk, Kuaishou and cross-platform frameworks (Taro / uni-app).
skill-sample/ ├─ SKILL.md ⭐ Required: skill entry doc (purpose / usage / examples / deps) ├─ manifest.sample.json ⭐ Recommended: machine-readable metadata (index / validation / autofill) ├─ LICENSE.sample ⭐ Recommended: license & scope (open source / restriction / commercial) ├─ scripts/ │ └─ example-run.py ✅ Runnable example script for quick verification ├─ assets/ │ ├─ example-formatting-guide.md 🧩 Output conventions: layout / structure / style │ └─ example-template.tex 🧩 Templates: quickly generate standardized output └─ references/ 🧩 Knowledge base: methods / guides / best practices ├─ example-ref-structure.md 🧩 Structure reference ├─ example-ref-analysis.md 🧩 Analysis reference └─ example-ref-visuals.md 🧩 Visual reference
More Agent Skills specs Anthropic docs: https://agentskills.io/home
├─ ⭐ Required: YAML Frontmatter (must be at top) │ ├─ ⭐ name : unique skill name, follow naming convention │ └─ ⭐ description : include trigger keywords for matching │ ├─ ✅ Optional: Frontmatter extension fields │ ├─ ✅ license : license identifier │ ├─ ✅ compatibility : runtime constraints when needed │ ├─ ✅ metadata : key-value fields (author/version/source_url...) │ └─ 🧩 allowed-tools : tool whitelist (experimental) │ └─ ✅ Recommended: Markdown body (progressive disclosure) ├─ ✅ Overview / Purpose ├─ ✅ When to use ├─ ✅ Step-by-step ├─ ✅ Inputs / Outputs ├─ ✅ Examples ├─ 🧩 Files & References ├─ 🧩 Edge cases ├─ 🧩 Troubleshooting └─ 🧩 Safety notes
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Quick Start:
Import/download skills (.zip/.skill), then place locally:
~/.claude/skills/ (Claude Code)
~/.codex/skills/ (Codex CLI)
One SKILL.md can be reused across tools.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.
Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.
Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.
This keeps agents lightweight while preserving enough context for complex tasks.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused across tools.
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills: