{
  "id": 17506687,
  "title": "A Project Skill Can Change APX Behavior With One Name",
  "url": "https://urgent.news/2026/11/01/a-project-skill-can-change-apx-behavior-with-one-name",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-01T01:03:52.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/agentprojectcontext/a-project-skill-can-change-apx-behavior-with-one-name-hae"
  },
  "original_language": "en",
  "account": "In the APX project management system, a project-local skill with the same name as a user-global or built-in skill takes precedence. This is useful when a repository requires its own set of operating rules. A project can supply its own version of a skill by creating a file named SKILL.md in the .apc/skills/ directory within the project. This file overrides the global or built-in version of the skill, providing a customized workflow for that specific project.\n\nFor instance, a personal release skill stored in ~/.apx/skills/release/SKILL.md might contain a checklist for normal releases, such as verifying tests, creating a tag, and writing release notes. However, a regulated service may require a different release process. By adding a file .apc/skills/release/SKILL.md within the project's repository, the project can establish its own release requirements, such as needing a change ticket, specifying a deployment window, and including a rollback note. APX will use this project-specific release skill instead of the personal one.\n\nIt is important to note that a project skill does not merge with the global or built-in version; instead, it replaces the lower-priority match. If the project version omits a critical step that is present in the global version, that step will be absent in the resolved skill. A common mistake is to use a generic skill name like review, test, or deploy, which can lead to collisions and inconsistent behavior across projects. To avoid this confusion, engineers should use a distinct name for additive or experimental guidance, clearly stating the scope of the skill in the description. This ensures that the project skill is reviewed in its entirety, rather than just comparing it to the global counterpart.",
  "summary": "A skill name is a boundary, not just a label. In APX, a project-local skill with the same slug as a user-global or built-in skill wins. That is useful when a repository needs its own operating rules. It is also a reason to treat a skill name change as a real behavior change. The precedence is deliberate APX builds its on-demand skill catalog from three places, in this order:…",
  "key_points": [
    "Project-local skill overrides user-global or built-in skill in APX",
    "Create SKILL.md file in .apc/skills/ directory to customize workflow",
    "Project-specific skill replaces global version, not merging with it"
  ],
  "editors_take": "Local skill overrides allow individual repositories to enforce specialized workflows, but the replacement mechanism requires careful naming to prevent accidental loss of critical global procedures during project execution.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}