Skip to content
Back to skills

Issue Assigner

ASecurity

Assign and unassign issues to users (CLI not yet available)

  • 666 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 9, 2026
toolsbashgit

Works with

  • cli

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill issue-assigner --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Issue Assigner?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Issue Assigner
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-issue-assigner/badge)](https://www.skillsdirectory.com/skills/majiayu000-issue-assigner)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: issue-assigner
description: Assign and unassign issues to users (CLI not yet available)
model: haiku
---

# 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`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.