--- name: amp-command-creator-bd6bd927d359 description: This skill must be used when users want to create custom slash commands. Activates with phrases like "create a command", "make a slash command", "add custom command", "create command for", or "automate with a command". --- # Amp Command Creator This skill guides the creation of custom Amp commands accessible via the Command Palette (Cmd/Alt-Shift-A in VS Code or Ctrl-O in CLI). ## What Amp Commands Do Amp commands append their output to the prompt input when invoked. They provide reusable prompts and automated workflows: - **Markdown commands** (.md files) — Static prompt templates inserted directly - **Executable commands** — Scripts that run and output dynamic content (can accept arguments) ## Command Locations Commands are discovered from various locations: 1. **Workspace-local**: `.agents/commands/` in the current workspace 2. **Global**: `~/.config/amp/commands` (or `$XDG_CONFIG_HOME/amp/commands` if set) 3. **Claude Code-compatible workspace**: `.claude/skills/` 4. **Claude Code-compatible global**: `~/.claude/skills/` Choose a location based on whether it is specific to the workspace, or would apply across workspaces. Only use the Claude code-compatible locations if the user specifically indicates they want it to work for all agents, not just Amp. The command name is derived from the filename (without extension). ## Command Types ### Type 1: Markdown Commands Static prompt templates that insert their contents directly. **When to use:** - Consistent prompts reused across sessions - System prompts, personas, or instruction sets - Review templates with fixed structure **Structure:** ```markdown # Command Title ## SYSTEM (optional) System-level instructions for Claude's behavior. ## ASSISTANT RULES (optional) Specific rules for how Claude should respond. ## OUTPUT FORMAT (optional) Expected structure of Claude's response. [Main prompt content...] ``` ### Type 2: Executable Commands Scripts that generate dynamic prompts based on context, arguments, or external data. **When to use:** - Commands that need runtime data (API calls, git state, file contents) - Commands accepting user arguments - Integration with external tools (Linear, GitHub, Jira) **Requirements:** - Must be executable (chmod +x) OR have shebang on first line - Output goes to stdout (combined with stderr, max 50k chars) - Can accept arguments passed at invocation **Shebang examples:** ```bash #!/bin/bash #!/usr/bin/env python3 #!/usr/bin/env node ``` ## Creation Process ### Step 1: Determine Command Type Ask clarifying questions: - "Should this command be static (same every time) or dynamic (changes based on context)?" - "Does it need to accept arguments?" - "Does it need to fetch data from external APIs or tools?" **Decision matrix:** | Need | Type | |------|------| | Static prompt | Markdown | | Accepts arguments | Executable | | Fetches external data | Executable | | Uses git/file state | Executable | ### Step 2: Determine Scope - **Workspace-local** (`.agents/commands/`) — Project-specific commands - **Global** (`~/.config/amp/commands`) — Commands available everywhere ### Step 3: Create the Command #### For Markdown Commands 1. Create the file at the appropriate location 2. Write clear, actionable instructions 3. Use sections (SYSTEM, ASSISTANT RULES, OUTPUT FORMAT) for complex prompts #### For Executable Commands 1. Create the script with proper shebang 2. Handle arguments via `$1`, `$2`, etc. (bash) or `sys.argv` (Python) 3. Output the prompt to stdout 4. Make executable: `chmod +x ` ### Step 4: Test the Command Instruct the user to: 1. Open Command Palette (Cmd/Alt-Shift-A or Ctrl-O) 2. Find and invoke the command 3. Verify the output appears in prompt input ## Best Practices ### Markdown Commands - Use clear section headers for organization - Include examples of expected output format - Keep system instructions concise but complete - Use fenced code blocks for structured output examples ### Executable Commands - Always validate required arguments exist - Provide helpful usage messages for missing args - Handle API errors gracefully with meaningful messages - Use environment variables for secrets (never hardcode) - Load .env files from project root when needed - Exit with non-zero code on errors ### General - Name commands descriptively: `pr-review`, `work-on-issue`, `daily-standup` - Document any required setup (API keys, dependencies) - Keep prompts focused on a single workflow ## Helper Script To initialize a new command with boilerplate, use: ```bash scripts/init_command.py --type [--scope ] ``` See `references/command-examples.md` for complete working examples including: - PR review template (Markdown) - Linear issue integration (Bash executable) --- Source attribution: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/amp-command-creator/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/amp-command-creator/SKILL.md Attribution basis: Source repository record Fields of work: Content & Media, Development & Engineering, Product Management Roles: Frontend Developer, Product Manager, Technical Writer Specialties: API Tools: Amp Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: cdc0e4ff8d6688f04fa9ab0bf65ccaa979e5ae45e01bfe1eee410567b7e45508