add-work

Automates GitHub issue creation and project board organization via Bash scripts and the GitHub CLI.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/eygraber/jellyfin-kmp --skill add-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-work
Source: https://github.com/eygraber/jellyfin-kmp/tree/main/.claude/skills/add-work
Command: npx skills add https://github.com/eygraber/jellyfin-kmp --skill add-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

Create and track work items by automatically generating GitHub issues from user prompts and organizing them on the project board.

Core Features & Use Cases

  • Create issues for features, bugs, epics, tasks, and chores with consistent labeling.
  • Automatically add issues to a project board and provide sub-epic linking for larger initiatives.
  • Use case: a product manager submits a feature request; the tool creates an issue with type feature and links related subtasks.

Quick Start

Invoke the add-work script with a type and title to create a new GitHub issue.

Frequently Asked Questions about add-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate creating GitHub issues and adding them to a project board?

You can automate creating GitHub issues and organizing them on a project board by running Bash scripts that use the GitHub CLI to generate issues, apply consistent labels, and place them directly onto your board.

Can I automatically link subissues to epics when creating GitHub issues?

Yes, you can link subissues to epics when creating GitHub issues. The automation uses the GitHub CLI to create epic-subissue relationships, allowing you to organize larger initiatives hierarchically on your project board.

What's the best way to apply consistent labels across features, bugs, and tasks in GitHub?

The best way to apply consistent labels across features, bugs, and tasks in GitHub is to use an automated script that assigns type-specific labels during issue creation, ensuring uniform categorization for project management.

Do I need the GitHub CLI to create issues and manage project boards automatically?

Yes, you need the GitHub CLI installed because the automation scripts rely on it to create issues, assign labels, add items to project boards, and link subissues. You also need jq for processing JSON data.

How does automated issue creation handle different work item types like chores and epics?

Automated issue creation handles different work item types by accepting a type parameter, such as chore or epic, and then applying the corresponding labels and project board placement rules to organize the generated GitHub issues consistently.

Are there limitations to automating GitHub project management tasks with Bash scripts?

A limitation of automating GitHub project management tasks with Bash scripts is that functionality is constrained by the capabilities of the GitHub CLI, meaning complex board configurations or custom fields may require additional manual setup or scripting.