Mpm Ticket View logo

Mpm Ticket View

Community
bobmatnyc
mpm-ticket-view

Orchestrate ticketing agent for project management workflows

Overview

Publisherbobmatnyc
Repositoryclaude-mpm
Skill namempm-ticket-view
Stars
152
Forks
34
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by bobmatnyc on GitHub. Read the source before you install it.

Installation

Install the Mpm Ticket View AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/bobmatnyc/claude-mpm.git /tmp/claude-mpm
mkdir -p .claude/skills
cp -r /tmp/claude-mpm/plugin/skills/mpm-ticket-view .claude/skills/mpm-ticket-view
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Mpm Ticket View in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Mpm Ticket View on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Mpm Ticket View is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

/mpm-ticket

High-level ticketing workflows delegating to ticketing agent.

Usage

/mpm-ticket <subcommand> [options]

CRITICAL: PM delegates ALL ticketing operations to ticketing agent. PM NEVER uses MCP tools directly.

Subcommands

/mpm-ticket organize

Review, transition states, update priorities, identify stale tickets.

MCP Tools (ticketing agent uses):

  • ticket_list, ticket_read, ticket_comment
  • ticket_transition, ticket_update
  • ticket_find_stale

Output: Tickets transitioned, priorities updated, stale tickets identified, next actions.

/mpm-ticket proceed

Analyze project board and recommend next actionable steps.

MCP Tools (ticketing agent uses):

  • project_status, ticket_list, ticket_search
  • epic_issues, get_available_transitions

Output: Project health, recommended next actions (top 3), blockers requiring attention.

/mpm-ticket status

Generate comprehensive status report covering work, tickets, project health.

MCP Tools (ticketing agent uses):

  • project_status, ticket_list, ticket_search
  • ticket_find_stale, get_my_tickets

Output: Health metrics, ticket counts, high-priority work, blockers, recent activity, risk assessment.

/mpm-ticket update

Create project status update (Linear ProjectUpdate).

MCP Tools (ticketing agent uses):

  • project_status, project_update_create
  • project_update_list, ticket_list

Output: Update ID, health status, accomplishments, metrics, risks, next sprint focus, published link.

/mpm-ticket project

Set project URL for context (Linear/GitHub/JIRA).

MCP Tools (ticketing agent uses):

  • config_set_default_project, epic_get, config_get

Output: Project context configured, platform/ID/name, access verified, summary.

Delegation Pattern

WRONG ❌:

# PM directly using MCP tools
result = mcp__mcp-ticketer__ticket_list()

CORRECT ✅:

# PM delegates to ticketing agent
PM: "I'll have ticketing organize tickets..."
[PM constructs delegation prompt]
[Ticketing agent uses MCP tools]
PM: [Presents results]

Fallback Strategy

If no ticketing MCP tools are available, ticketing agent falls back to gh CLI (GitHub Issues):

bash
gh issue list
gh issue view ISSUE-NUMBER
gh issue close ISSUE-NUMBER

PM still delegates - ticketing agent handles CLI fallback internally.

Example Workflows

bash
# Organize and analyze
/mpm-ticket organize          # Clean up board
/mpm-ticket proceed           # Get next steps

# Weekly update
/mpm-ticket update            # Create status update

# Project setup
/mpm-ticket project https://linear.app/team/project/abc-123

See docs/commands/ticket.md for comprehensive documentation.

Frequently asked questions

What does the Mpm Ticket View AI skill do?

Orchestrate ticketing agent for project management workflows

Why use Mpm Ticket View on TypingMind?

Because you install it once and use it with any model. Mpm Ticket View is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Mpm Ticket View in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/bobmatnyc/claude-mpm/tree/main/plugin/skills/mpm-ticket-view. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Mpm Ticket View?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Mpm Ticket View?

As many as you like. As long as a model supports skills, you can use Mpm Ticket View with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Mpm Ticket View AI skill free?

It is published on GitHub by bobmatnyc. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇