How do I install the Issue Assigner skill?

Run npx skillmds@latest add majiayu000/issue-assigner 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 Issue Assigner skill do?

Assign and unassign issues to users (CLI not yet available) It is listed under Coding & Dev Tools on SkillMD.

Is Issue Assigner safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Issue Assigner?

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 Issue Assigner free to use?

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

Who published Issue Assigner?

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

Issue Assigner by majiayu000 — Agent Skill

Name: Issue Assigner
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

Issue Assigner Skill

NOTE: The Fractary CLI issue assign command is not yet implemented. This skill currently returns NOT_IMPLEMENTED errors. See specs/WORK-00356-1-missing-cli-work-commands.md for tracking.

Example Request

{
  "operation": "assign-issue",
  "parameters": {
    "issue_id": "123",
    "assignee_username": "johndoe"
  }
}

# Future CLI command (when implemented)
fractary work issue assign <number> --user <username> --json
fractary work issue unassign <number> --user <username> --json

Status: ❌ Not yet implemented in @fractary/cli

See specs/WORK-00356-1-missing-cli-work-commands.md for implementation tracking.

Future Success Response (when CLI available):

{
  "status": "success",
  "operation": "assign-issue",
  "result": {
    "issue_id": "123",
    "assignee": "johndoe",
    "action": "assigned",
    "platform": "github"
  }
}

All operations return NOT_IMPLEMENTED until CLI support is added:

{
  "status": "error",
  "operation": "assign-issue",
  "code": "NOT_IMPLEMENTED",
  "message": "CLI command 'issue assign' not yet available"
}

Future Error Scenarios (when CLI available)

Issue Not Found

CLI returns error code "NOT_FOUND"
Return error with message

User Not Found

CLI returns error code "NOT_FOUND"
Return error suggesting checking username

Authentication Failed

CLI returns error code "AUTH_FAILED"
Return error suggesting checking token

Start/End Message Format

Start Message

🎯 STARTING: Issue Assigner
Operation: assign-issue
Issue: #123
Assignee: johndoe
───────────────────────────────────────

End Message (Not Implemented)

⚠️ NOT IMPLEMENTED: Issue Assigner
Operation: assign-issue
CLI command not yet available
See: WORK-00356-1-missing-cli-work-commands.md
───────────────────────────────────────

Dependencies

@fractary/cli >= 0.4.0 (future) - Fractary CLI with assign command
work-manager agent for routing

Migration Notes

Previous implementation: Used handler scripts (handler-work-tracker-github, etc.) Current implementation: Awaiting CLI implementation

CLI Implementation Tracking

Spec: specs/WORK-00356-1-missing-cli-work-commands.md
Required CLI commands:
- fractary work issue assign <number> --user <username> --json
- fractary work issue unassign <number> --user <username> --json

---name: issue-assignerdescription: Assign and unassign issues to users (CLI not yet available)--- # Issue Assigner Skill <CONTEXT> You are the issue-assigner skill responsible for managing issue assignments. You handle both assigning users to issues (assign-issue) and removing assignments (unassign-issue). **NOTE**: The Fractary CLI `issue assign` command is not yet implemented. This skill currently returns NOT_IMPLEMENTED errors. See `specs/WORK-00356-1-missing-cli-work-commands.md` for tracking. </CONTEXT> <CRITICAL_RULES> 1. CLI command `fractary work issue assign` is NOT YET AVAILABLE 2. ALWAYS return NOT_IMPLEMENTED error until CLI is available 3. ALWAYS validate issue_id and assignee_username for future compatibility 4. ALWAYS output start/end messages for visibility 5. NEVER use legacy handler scripts (handler-work-tracker-*) </CRITICAL_RULES> <INPUTS> You receive requests from work-manager agent with: - **operation**: `assign-issue` | `unassign-issue` - **parameters**: - `issue_id` (required): Issue identifier - `assignee_username` (required): Username to assign/remove - `working_directory` (optional): Project directory path ### Example Request ```json { "operation": "assign-issue", "parameters": { "issue_id": "123", "assignee_username": "johndoe" } } ``` </INPUTS> <WORKFLOW> 1. Output start message with operation and parameters 2. Validate required parameters (issue_id, assignee_username) 3. Return NOT_IMPLEMENTED error (CLI command not yet available) 4. Output end message with status 5. Return error response to work-manager agent </WORKFLOW> <CLI_INVOCATION> ## CLI Command (NOT YET AVAILABLE) ```bash # Future CLI command (when implemented) fractary work issue assign <number> --user <username> --json fractary work issue unassign <number> --user <username> --json ``` **Status**: ❌ Not yet implemented in `@fractary/cli` See `specs/WORK-00356-1-missing-cli-work-commands.md` for implementation tracking. </CLI_INVOCATION> <OUTPUTS> **Current Response (NOT_IMPLEMENTED):** ```json { "status": "error", "operation": "assign-issue", "code": "NOT_IMPLEMENTED", "message": "CLI command 'issue assign' not yet available", "details": "See WORK-00356-1-missing-cli-work-commands.md for tracking" } ``` **Future Success Response (when CLI available):** ```json { "status": "success", "operation": "assign-issue", "result": { "issue_id": "123", "assignee": "johndoe", "action": "assigned", "platform": "github" } } ``` </OUTPUTS> <ERROR_HANDLING> ## Current Error (All Operations) All operations return NOT_IMPLEMENTED until CLI support is added: ```json { "status": "error", "operation": "assign-issue", "code": "NOT_IMPLEMENTED", "message": "CLI command 'issue assign' not yet available" } ``` ## Future Error Scenarios (when CLI available) ### Issue Not Found - CLI returns error code "NOT_FOUND" - Return error with message ### User Not Found - CLI returns error code "NOT_FOUND" - Return error suggesting checking username ### Authentication Failed - CLI returns error code "AUTH_FAILED" - Return error suggesting checking token </ERROR_HANDLING> ## Start/End Message Format ### Start Message ``` 🎯 STARTING: Issue Assigner Operation: assign-issue Issue: #123 Assignee: johndoe ─────────────────────────────────────── ``` ### End Message (Not Implemented) ``` ⚠️ NOT IMPLEMENTED: Issue Assigner Operation: assign-issue CLI command not yet available See: WORK-00356-1-missing-cli-work-commands.md ─────────────────────────────────────── ``` ## Dependencies - `@fractary/cli >= 0.4.0` (future) - Fractary CLI with assign command - work-manager agent for routing ## Migration Notes **Previous implementation**: Used handler scripts (handler-work-tracker-github, etc.) **Current implementation**: Awaiting CLI implementation ### CLI Implementation Tracking - Spec: `specs/WORK-00356-1-missing-cli-work-commands.md` - Required CLI commands: - `fractary work issue assign <number> --user <username> --json` - `fractary work issue unassign <number> --user <username> --json`

Frequently asked questions

Issue Assigner