Skip to main content

psm-session-metadata

Manage Pi Session Manager workflow Status and GitHub-style Labels for the current Pi session. Use when the user asks to organize, classify, triage, label, tag, move, mark, or inspect the current session's Kanban status or labels.

Informações da origem

Repositório
dwsy/pi-session-manager
Última atividade na origem
5 de setembro de 2026 às 12:22
Idioma detectado do SKILL.md
inglês
Estrelas
190
Forks
15

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
name
psm-session-metadata
description
Manage Pi Session Manager workflow Status and GitHub-style Labels for the current Pi session. Use when the user asks to organize, classify, triage, label, tag, move, mark, or inspect the current session's Kanban status or labels.
# PSM Session Metadata Use the Pi Session Manager tools registered by this extension. Status and Labels are separate metadata systems and must stay separate. ## Workflow Status A session has at most one workflow Status. - Inspect available statuses and the current assignment with `session_status` action `list`. - Assign a status with `session_status` action `set` and `status` set to the requested name. - Clear it with `session_status` action `clear`. - If the requested status does not exist, `set` creates it. ## Labels A session may have multiple GitHub-style Labels. - Inspect available and assigned labels with `session_label` action `list`. - Assign with `session_label` action `set` and `label` set to the requested name. - Remove with `session_label` action `remove`. - When creating a new label, optional `color` must be `#RRGGBB`; optional `description` explains its purpose. ## Rules - Do not use workflow Status as a substitute for Labels or vice versa. - Prefer existing names returned by the list actions before creating new metadata. - For ambiguous requests such as "mark this done", inspect statuses first and choose the matching existing workflow Status. - For descriptive classifications such as `bug`, `frontend`, or `urgent`, use Labels unless the user explicitly calls it a workflow status. - Report the resulting Status/Labels after changing them.
Ver no GitHub