Skip to content
Skills Library
Management & product · Tool integration

myopenpanels-task-queue

/myopenpanels-task-queue

Use when inspecting or managing work in the MyOpenPanels project Task queue, or executing a Studio-provided Task Handoff.

Repository
OpenPanels ↗
Licence
MIT
Last repository change
31.07.2026

Assessment and security

82/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content17 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
6
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 31.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when inspecting or managing work in the MyOpenPanels project Task queue, or executing a Studio-provided Task Handoff.

Original author description

Use when inspecting or managing work in the MyOpenPanels project Task queue, or executing a Studio-provided Task Handoff.

How it works

SKILL.md has no level-two headings · 45 lines, 360 words

SKILL.md preview
---
name: myopenpanels-task-queue
description: Use when inspecting or managing work in the MyOpenPanels project Task queue, or executing a Studio-provided Task Handoff.
---

Use the generic Task commands returned by command catalog discovery. The `tasks`
table and generic Task service are authoritative; do not call queue-specific
HTTP endpoints or mutate panel state to change a Task lifecycle.

Intent routing:

- For read-only Task state and its embedded execution summaries, read
  `references/inspect.md`.
- To retry a failed Task, read `references/retry.md`.
- To cancel a Task, read `references/cancel.md`.
- To archive a terminal Task, read `references/archive.md`.
- For an exact Studio Task scope handoff, read `references/execute-scope.md`.

1. Run the exact `task handoff start` selector supplied by Studio. It registers
   and claims on execution, not when the instruction is copied.
2. Follow the returned ExecutionBundle and Delivery Contract without separately
   loading Catalogs, Panel Skills, or portable Skills.
3. Write only the declared workspace artifacts and `execution-result.json`.
   Use `task handoff exec` only for commands explicitly allowed by the Bundle;
   it injects the private Broker and fencing context.
4. Heartbeat long work through `task handoff heartbeat`. Stop immediately when
   heartbeat or a work command returns `execution_fenced`.
5. Finish through `task handoff complete` or `task handoff fail`. The Runtime
   validates the result, stages declared outputs, and completes the
   Task, and immediately returns the next Bundle when the scope can continue.
6. Exit only at `complete` or `blocked`; use `task handoff stop` to abandon and
   release active work. Do not run low-level claim, complete, fail, or release
   commands for a handoff.

Use `task next` only for read-only discovery. A runnable Task has `ready: true`;
a Task can be blocked by a live lease, a future retry time, exhausted executions,
or the lack of an available Agent CLI. Persistent queue execution is owned by
the Studio Worker. Manual Agents process only the supplied execution scope.
`exact-task` selects only the named Task. `project-drain`
continues independent runnable Tasks before reporting blockers.
`wiki-mutation-drain` processes one prerequisite or mutation Task at a time in
mutation order until the mutation queue is empty.

Never treat process exit zero as proof of success. `task handoff complete`
performs the Handler's domain validation. A rejected completion is a failed
execution; stop task-bound writes as soon as the execution is fenced. Use
`task read` when diagnosing
prerequisite propagation or retries.
Files in this package (6)
  • SKILL.md 3 KB
  • references/archive.md 1 KB
  • references/cancel.md 1 KB
  • references/execute-scope.md 1 KB
  • references/inspect.md 1 KB
  • references/retry.md 1 KB

Versions

The database has no other skills named myopenpanels-task-queue.

Database snapshot: 13.11.2026 · package version 4d37df69bc25 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100myopenpanels
    Use MyOpenPanels for persistent visual, knowledge, writing, typesetting, or publishing work in its Canvas, Wiki, Writing, Typesetting, or Publishing panel, including drawing, image work, diagrams, moodboards, brainstorming, organizing, research, drafting, writing, layout, and…
  • 100pm-status
    Use when the user asks for project status, a one-screen summary, or the queue of work for themselves. Shows the summary or the user's queue. Read-only.
  • 90pick
    Pick a task from the work queue (`ravenseat`) and do it yourself in this session, following the same protocol as a queue track. Use when the user types "/pick" (suggestions for what can be picked now) or "/pick <id>" (take exactly that task), or says "pick a task", "what can I…
  • 100task-status
    Read-only taskwarrior queue report — pending, blocked, ready tasks and drift vs linked PRs. Use when auditing queue health, orienting before a wave, or for standup summaries.
  • 86hoo-task-board
    Use to view or mirror the work queue - "task board", "show the queue", /organic-os:task-board. Mirrors to Notion when that connector exists; local queue.md is the source of truth.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.