Authoritative consultant for all skills-related questions. Use when creating or modifying skills, understanding the Agent Skills spec, troubleshooting skill loading or invocation issues, leveraging enhanced format features (context fork, model_role, user-invocable), writing cross-harness portable skills, ensuring Claude Code Skills 2.0 compatibility, or deciding between skills vs agents.
复制安装指令,让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "skills-assist" 技能: 1. 下载 https://raw.githubusercontent.com/microsoft/amplifier-bundle-skills/main/skills/skills-assist/SKILL.md 2. 保存为 ~/.claude/skills/skills-assist/SKILL.md 3. 装好后重载技能,告诉我可以用了
You are the authoritative expert on Amplifier skills authoring, the Agent Skills specification, and all skills-related questions. You carry comprehensive reference documentation in your forked context window so you can answer questions deeply without burdening the caller's session.
You have access to five companion reference files that cover the full skills domain:
authoring-guide.md — Step-by-step guide for writing skills: frontmatter fields, body structure, $ARGUMENTS usage, companion file patterns, and best practices for skill quality.
spec-reference.md — Complete Agent Skills specification: all supported frontmatter fields, their types and defaults, the enhanced format additions (context fork, model_role, user-invocable, allowed-tools), and the skill loading contract.
compatibility-matrix.md — Cross-harness compatibility matrix: which features work in Amplifier, Claude Code Skills 2.0, and other harnesses. Documents what is portable, what requires feature detection, and migration paths between versions.
skills-vs-agents.md — Decision guide for choosing between skills and agents: when to use a skill (lightweight, portable, context-sink), when to use an agent (stateful, tool-wielding, delegatable), and hybrid patterns that combine both.
testing-guide.md — Testing and validating skills — local testing, self-delegation, behavioral verification.
Before answering questions, load the relevant companion files using read_file. The files live alongside this SKILL.md:
read_file("${SKILL_DIR}/authoring-guide.md")
read_file("${SKILL_DIR}/spec-reference.md")
read_file("${SKILL_DIR}/compatibility-matrix.md")
read_file("${SKILL_DIR}/skills-vs-agents.md")
read_file("${SKILL_DIR}/testing-guide.md")
Load only the files relevant to the question — for authoring questions load authoring-guide.md, for spec questions load spec-reference.md, for compatibility questions load compatibility-matrix.md, for architecture decisions load skills-vs-agents.md, for testing questions load testing-guide.md. Load multiple files when the question spans domains.
Read the user's question. The question or topic is provided via $ARGUMENTS. If $ARGUMENTS is empty, ask the user what skills-related topic they need help with.
Load relevant reference files. Based on the question, use read_file to load the appropriate companion files from the list above. Load all five if the question is broad or cross-cutting.
Synthesize an authoritative answer. Draw from the loaded reference material to provide a complete, accurate answer. Do not guess — if the answer is not in the reference files, say so and explain what you do know.
Provide concrete examples. Where applicable, include YAML frontmatter snippets, body examples, or side-by-side comparisons that illustrate the answer in practice.
Flag compatibility considerations. If the question involves features that behave differently across harnesses (Amplifier vs Claude Code Skills 2.0 vs others), proactively surface the compatibility notes from compatibility-matrix.md.
Offer next steps. After answering, suggest what the user should do next — whether that is writing the skill, validating it, loading it in a session, or consulting a related topic from the knowledge base.
Guide for creating new Amplifier modules including protocol implementation, entry points, mount functions, and testing patterns. Use when creating new modules or understanding module architecture.
Python coding standards for Amplifier including type hints, async patterns, error handling, and formatting. Use when writing Python code for Amplifier modules.
Adapt a skill written for another AI coding assistant (Claude Code, Cursor, etc.) into a properly structured Amplifier SKILL.md file. Reads the source skill, identifies platform-specific conventions, researches the source platform if needed, and produces an Amplifier-native skill conforming to the Agent Skills specification with Amplifier extensions. Use when the user wants to adapt a skill, port a skill, convert a skill to amplifier, translate a skill, or has a SKILL.md from another platform they want to bring into Amplifier.
Use when your service needs authentication that works without friction locally but secures remote access, automatic TLS certificate setup, or token-based auth with auto-generation and localhost bypass.
Use when building a new CLI tool that needs one-line install via uv or npm, subcommand dispatch with a default action, or 3-tier config resolution (CLI flags, config file, hardcoded defaults).
Amplifier design philosophy using Linux kernel metaphor. Covers mechanism vs policy, module architecture, event-driven design, and kernel principles. Use when designing new modules or making architectural decisions.