How do I install the Aim Projects skill?

Run npx skillmds@latest add brianv1981/aim-projects in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Aim Projects skill do?

Interacts with the GitHub Projects kanban board natively using the `gh` CLI on Windows. It is listed under Coding & Dev Tools on SkillMD.

Is Aim Projects safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aim Projects?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aim Projects free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aim Projects?

BrianV1981 (@brianv1981) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aim Projects by brianv1981 — Agent Skill

Name: Aim Projects
Author: BrianV1981

File contents

`aim-projects`

MANDATE: Use the native GitHub CLI (gh) to read and update the shared Kanban board (the source of truth for multi-agent work). Never invent board state offline.

PREREQUISITES

The host must have the project scope authorized. If any commands fail with scope errors, instruct the operator to run: gh auth refresh -s project,read:project

Configuration required (fetch these from environment or operator):

AIM_PROJECTS_OWNER (e.g., @me or an org name)
AIM_PROJECTS_NUMBER (e.g., 5)

1. See the Board (List Items)

To view the current kanban state, you must list the items in the project:

gh project item-list <PROJECT_NUMBER> --owner <OWNER> --format json

Note: Parsing the JSON output is required to find specific Issue Item IDs and their current statuses.

2. Claim Work (In Progress)

Before coding, you MUST claim the issue so other agents share the same page. To update an item's status, you need the Project ID, Item ID, the ID of the Status field, and the Option ID for the specific status.

Fetch Project ID: gh project view <PROJECT_NUMBER> --owner <OWNER> --format json
Fetch Field ID and Option IDs for "Status": gh project field-list <PROJECT_NUMBER> --owner <OWNER> --format json. Parse the JSON to find the id of the "Status" field and the id of the specific status option (e.g. "In progress", "Done") within its options array.

Update Status using the single-select-option-id flag:

gh project item-edit --id <ITEM_ID> --field-id <STATUS_FIELD_ID> --project-id <PROJECT_ID> --single-select-option-id <OPTION_ID>

3. Ship (Done)

After your PR is shipped or the branch is promoted via aim-gitops, you must move the issue to Done:

gh project item-edit --id <ITEM_ID> --field-id <STATUS_FIELD_ID> --project-id <PROJECT_ID> --single-select-option-id <DONE_OPTION_ID>

4. Blocked

When waiting on the Operator, DNS changes, or external factors:

gh project item-edit --id <ITEM_ID> --field-id <STATUS_FIELD_ID> --project-id <PROJECT_ID> --single-select-option-id <BLOCKED_OPTION_ID>

---name: aim-projectsdescription: Interacts with the GitHub Projects kanban board natively using the `gh` CLI on Windows.---# `aim-projects`> **MANDATE:** Use the native GitHub CLI (`gh`) to read and update the shared Kanban board (the source of truth for multi-agent work). Never invent board state offline.## PREREQUISITESThe host must have the project scope authorized. If any commands fail with scope errors, instruct the operator to run:`gh auth refresh -s project,read:project`Configuration required (fetch these from environment or operator):- `AIM_PROJECTS_OWNER` (e.g., `@me` or an org name)- `AIM_PROJECTS_NUMBER` (e.g., `5`)## 1. See the Board (List Items)To view the current kanban state, you must list the items in the project:```powershellgh project item-list <PROJECT_NUMBER> --owner <OWNER> --format json```*Note: Parsing the JSON output is required to find specific Issue Item IDs and their current statuses.*## 2. Claim Work (In Progress)Before coding, you MUST claim the issue so other agents share the same page.To update an item's status, you need the Project ID, Item ID, the ID of the Status field, and the Option ID for the specific status.1. Fetch Project ID: `gh project view <PROJECT_NUMBER> --owner <OWNER> --format json`2. Fetch Field ID and Option IDs for "Status": `gh project field-list <PROJECT_NUMBER> --owner <OWNER> --format json`. Parse the JSON to find the `id` of the "Status" field and the `id` of the specific status option (e.g. "In progress", "Done") within its `options` array.3. Update Status using the single-select-option-id flag: ```powershell gh project item-edit --id <ITEM_ID> --field-id <STATUS_FIELD_ID> --project-id <PROJECT_ID> --single-select-option-id <OPTION_ID> ```## 3. Ship (Done)After your PR is shipped or the branch is promoted via `aim-gitops`, you must move the issue to Done:```powershellgh project item-edit --id <ITEM_ID> --field-id <STATUS_FIELD_ID> --project-id <PROJECT_ID> --single-select-option-id <DONE_OPTION_ID>```## 4. BlockedWhen waiting on the Operator, DNS changes, or external factors:```powershellgh project item-edit --id <ITEM_ID> --field-id <STATUS_FIELD_ID> --project-id <PROJECT_ID> --single-select-option-id <BLOCKED_OPTION_ID>```

Frequently asked questions

Aim Projects