{
  "@context": "https://schema.org",
  "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-01-29-slashing-custom-commands/#webpage",
  "@type": [
    "WebPage",
    "ArchiveComponent"
  ],
  "articleBody": "We're removing custom commands in favor of [skills](https://ampcode.com/manual#agent-skills). They were two ways of doing the same thing, except that only you could invoke custom commands, and only the agent could invoke skills. Now that you can invoke skills directly, there's no reason to keep custom commands around anymore.\n\n## Migrating Custom Commands to Skills\n\nIt's easy and takes just a few minutes.\n\n### Let Amp Do It For You\n\nIf you have custom commands in `.agents/commands/` or `~/.config/amp/commands/`, ask Amp to migrate them for you with the following prompt:\n\n```\nMigrate my custom commands from .agents/commands/ to skills in .agents/skills.\n\nFor each command:\n1. Create a new skill directory in .agents/skills/ named after the command\n2. If it's a markdown file, rename it to SKILL.md and add frontmatter with name and description\n3. If it's an executable, create a SKILL.md that describes when and how to run the script, and move the executable to a scripts/ subdirectory\n4. Delete the original command file\n\nAlso do this for global custom commands in ~/.config/amp/commands (which should be migrated to skills ~/.config/agents/skills).\n```\n\n### Or Do It Manually\n\n**Markdown commands:** Move your `.md` file to a skill directory:\n\n```\n# Before\n.agents/commands/code-review.md\n\n# After\n.agents/skills/code-review/SKILL.md\n```\n\nAdd frontmatter:\n\n```markdown\n---\nname: code-review\ndescription: Review code for quality and best practices\n---\n\n[Your existing content]\n```\n\n**Executable commands:** Move the executable into a `scripts/` subdirectory:\n\n```\n# Before\n.agents/commands/deploy\n\n# After\n.agents/skills/deploy/\n├── SKILL.md\n└── scripts/\n    └── deploy\n```\n\nIn `SKILL.md`, tell the agent how to use it:\n\n```markdown\n---\nname: deploy\ndescription: Deploy the application\n---\n\nRun `{baseDir}/scripts/deploy` to deploy.\n```\n",
  "authors": [],
  "captured_at": "2026-10-03T23:09:50.514863041+00:00",
  "category": "programming",
  "content_html": "<p>We're removing custom commands in favor of <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/manual#agent-skills\">skills</a>. They were two ways of doing the same thing, except that only you could invoke custom commands, and only the agent could invoke skills. Now that you can invoke skills directly, there's no reason to keep custom commands around anymore.</p>\n<h2>Migrating Custom Commands to Skills</h2>\n<p>It's easy and takes just a few minutes.</p>\n<h3>Let Amp Do It For You</h3>\n<p>If you have custom commands in <code>.agents/commands/</code> or <code>~/.config/amp/commands/</code>, ask Amp to migrate them for you with the following prompt:</p>\n<pre><code><span class=\"code-snippet\">Migrate my custom commands from .agents/commands/ to skills in .agents/skills.\n\nFor each command:\n1. Create a new skill directory in .agents/skills/ named after the command\n2. If it&#39;s a markdown file, rename it to SKILL.md and add frontmatter with name and description\n3. If it&#39;s an executable, create a SKILL.md that describes when and how to run the script, and move the executable to a scripts/ subdirectory\n4. Delete the original command file\n\nAlso do this for global custom commands in ~/.config/amp/commands (which should be migrated to skills ~/.config/agents/skills).\n</span></code></pre>\n<h3>Or Do It Manually</h3>\n<p><strong>Markdown commands:</strong> Move your <code>.md</code> file to a skill directory:</p>\n<pre><code><span class=\"code-snippet\"># Before\n.agents/commands/code-review.md\n\n# After\n.agents/skills/code-review/SKILL.md\n</span></code></pre>\n<p>Add frontmatter:</p>\n<pre><code class=\"language-markdown\"><span class=\"code-snippet\" data-language=\"Markdown\"><span class=\"syntax-text syntax-html syntax-markdown\"><span class=\"syntax-meta syntax-block-level syntax-markdown\"><span class=\"syntax-meta syntax-separator syntax-thematic-break syntax-markdown\"><span class=\"syntax-punctuation syntax-definition syntax-thematic-break syntax-markdown\">---</span>\n</span></span><span class=\"syntax-meta syntax-paragraph syntax-markdown\">name: code-review\ndescription: Review code for quality and best practices\n<span class=\"syntax-markup syntax-heading syntax-2 syntax-setext syntax-markdown\"><span class=\"syntax-punctuation syntax-definition syntax-heading syntax-setext syntax-markdown\">---</span></span></span>\n\n<span class=\"syntax-meta syntax-paragraph syntax-markdown\">[Your existing content]\n</span></span></span></code></pre>\n<p><strong>Executable commands:</strong> Move the executable into a <code>scripts/</code> subdirectory:</p>\n<pre><code><span class=\"code-snippet\"># Before\n.agents/commands/deploy\n\n# After\n.agents/skills/deploy/\n├── SKILL.md\n└── scripts/\n    └── deploy\n</span></code></pre>\n<p>In <code>SKILL.md</code>, tell the agent how to use it:</p>\n<pre><code class=\"language-markdown\"><span class=\"code-snippet\" data-language=\"Markdown\"><span class=\"syntax-text syntax-html syntax-markdown\"><span class=\"syntax-meta syntax-block-level syntax-markdown\"><span class=\"syntax-meta syntax-separator syntax-thematic-break syntax-markdown\"><span class=\"syntax-punctuation syntax-definition syntax-thematic-break syntax-markdown\">---</span>\n</span></span><span class=\"syntax-meta syntax-paragraph syntax-markdown\">name: deploy\ndescription: Deploy the application\n<span class=\"syntax-markup syntax-heading syntax-2 syntax-setext syntax-markdown\"><span class=\"syntax-punctuation syntax-definition syntax-heading syntax-setext syntax-markdown\">---</span></span></span>\n\n<span class=\"syntax-meta syntax-paragraph syntax-markdown\">Run <span class=\"syntax-markup syntax-raw syntax-inline syntax-markdown\"><span class=\"syntax-punctuation syntax-definition syntax-raw syntax-begin syntax-markdown\">`</span>{baseDir}/scripts/deploy<span class=\"syntax-punctuation syntax-definition syntax-raw syntax-end syntax-markdown\">`</span></span> to deploy.\n</span></span></span></code></pre>\n",
  "content_markdown": "We're removing custom commands in favor of [skills](https://ampcode.com/manual#agent-skills). They were two ways of doing the same thing, except that only you could invoke custom commands, and only the agent could invoke skills. Now that you can invoke skills directly, there's no reason to keep custom commands around anymore.\n\n## Migrating Custom Commands to Skills\n\nIt's easy and takes just a few minutes.\n\n### Let Amp Do It For You\n\nIf you have custom commands in `.agents/commands/` or `~/.config/amp/commands/`, ask Amp to migrate them for you with the following prompt:\n\n```\nMigrate my custom commands from .agents/commands/ to skills in .agents/skills.\n\nFor each command:\n1. Create a new skill directory in .agents/skills/ named after the command\n2. If it's a markdown file, rename it to SKILL.md and add frontmatter with name and description\n3. If it's an executable, create a SKILL.md that describes when and how to run the script, and move the executable to a scripts/ subdirectory\n4. Delete the original command file\n\nAlso do this for global custom commands in ~/.config/amp/commands (which should be migrated to skills ~/.config/agents/skills).\n```\n\n### Or Do It Manually\n\n**Markdown commands:** Move your `.md` file to a skill directory:\n\n```\n# Before\n.agents/commands/code-review.md\n\n# After\n.agents/skills/code-review/SKILL.md\n```\n\nAdd frontmatter:\n\n```markdown\n---\nname: code-review\ndescription: Review code for quality and best practices\n---\n\n[Your existing content]\n```\n\n**Executable commands:** Move the executable into a `scripts/` subdirectory:\n\n```\n# Before\n.agents/commands/deploy\n\n# After\n.agents/skills/deploy/\n├── SKILL.md\n└── scripts/\n    └── deploy\n```\n\nIn `SKILL.md`, tell the agent how to use it:\n\n```markdown\n---\nname: deploy\ndescription: Deploy the application\n---\n\nRun `{baseDir}/scripts/deploy` to deploy.\n```\n",
  "dateCreated": "2026-10-03T23:09:50.514863041+00:00",
  "date_created": "2026-01-29T00:00:00+00:00",
  "date_modified": "2026-01-29T00:00:00+00:00",
  "date_published": "2026-01-29T00:00:00+00:00",
  "description": "We're removing custom commands in favor of skills. They were two ways of doing the same thing, except that only you could invoke custom commands, and only the agent could invoke skills. Now that you can invoke skills directly, there's no…",
  "external_url": "https://ampcode.com/news/slashing-custom-commands",
  "git": {
    "commit": "ebb0941c5c06a2ab2377342d607535262a3e969e",
    "path": "items/ampcode-com/2026/01/2026-01-29-slashing-custom-commands.md",
    "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/ebb0941c5c06a2ab2377342d607535262a3e969e/items/ampcode-com/2026/01/2026-01-29-slashing-custom-commands.md"
  },
  "id": "urn:aggr:item:eaf2e36ecf0f39fa61d3f1f0f670deae4717fb68",
  "isBasedOn": {
    "@id": "https://ampcode.com/news/slashing-custom-commands"
  },
  "mainEntity": {
    "@id": "https://ampcode.com/news/slashing-custom-commands",
    "@type": "CreativeWork",
    "archivedAt": {
      "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-01-29-slashing-custom-commands/#webpage"
    },
    "dateModified": "2026-01-29T00:00:00+00:00",
    "datePublished": "2026-01-29T00:00:00+00:00",
    "headline": "Slashing Custom Commands",
    "timeRequired": "PT2M",
    "url": "https://ampcode.com/news/slashing-custom-commands",
    "wordCount": 268
  },
  "name": "Archived snapshot: Slashing Custom Commands",
  "preview": null,
  "reading_minutes": 2,
  "replicated_at": null,
  "source": "ampcode-com",
  "source_name": "Amp News",
  "summary": "We're removing custom commands in favor of skills. They were two ways of doing the same thing, except that only you could invoke custom commands, and only the agent could invoke skills. Now that you can invoke skills directly, there's no reason to keep custom commands around anymore. Migrating Custom Commands to Skills It's easy and takes just a few minutes. Let Amp Do It For You If you have custom commands in .agents/commands/ or ~/.config/amp/commands/, ask Amp to migrate them for you with the following prompt: Migrate my custom commands from .agents/commands/ to skills in .agents/skills. For each command: 1. Create a new skill directory in .agents/skills/ named after the command 2. If it's a markdown file, rename it to SKILL.md and add frontmatter with name and description 3. If it's an executable, create a SKILL.md that describes when and how to run the script, and move the executable to a scripts/ subdirectory 4. Delete the original command file Also do this for global custom commands in ~/.config/amp/commands (which should be migrated to skills ~/.config/agents/skills). Or Do It Manually Markdown commands: Move your .md file to a skill directory: # Before .agents/commands/code-review.md # After .agents/skills/code-review/SKILL.md Add frontmatter: --- name: code-review description: Review code for quality and best practices --- [Your existing content] Executable commands: Move the executable into a scripts/ subdirectory: # Before .agents/commands/deploy # After .agents/skills/deploy/ ├── SKILL.md └── scripts/ └── deploy In SKILL.md, tell the agent how to use it: --- name: deploy description: Deploy the application --- Run `{baseDir}/scripts/deploy` to deploy.",
  "tags": [],
  "temporalCoverage": "2026-10-03T23:09:50.514863041+00:00",
  "title": "Slashing Custom Commands",
  "url": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-01-29-slashing-custom-commands/",
  "word_count": 268
}