Skip to content
Skills Library
AI & agents · Automation

take-task

/take-task

Safely claim a specific or next eligible kotgent task from a free session, detect blocked or concurrent work, and immediately continue through the work-task workflow. Use when the user asks to take, claim, pick up, start, or work the next kotgent task, optionally naming a task ref.

Author
Heapy ↗
Repository
kortex ↗
Licence
Apache-2.0
Last repository change
22.10.2026

Assessment and security

100/ 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.
Content35 / 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
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

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

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Safely claim a specific or next eligible kotgent task from a free session, detect blocked or concurrent work, and immediately continue through the work-task workflow. Use when the user asks to take, claim, pick up, start, or work the next kotgent task, optionally naming a task ref.

Original author description

Safely claim a specific or next eligible kotgent task from a free session, detect blocked or concurrent work, and immediately continue through the work-task workflow. Use when the user asks to take, claim, pick up, start, or work the next kotgent task, optionally naming a task ref.

How it works

  1. Resolve the caller identity
  2. Resolve a candidate
  3. Detect parallel work after claiming
Original SKILL.md headings · 91 lines, 647 words
SKILL.md preview
---
name: take-task
description: Safely claim a specific or next eligible kotgent task from a free session, detect blocked or concurrent work, and immediately continue through the work-task workflow. Use when the user asks to take, claim, pick up, start, or work the next kotgent task, optionally naming a task ref.
disable-model-invocation: true
---

# Take Task

Claim work only from a free kotgent session. Use the `kotgent` CLI for tracker operations and `git` for
repository state. Do not use an MCP server, SDK, direct daemon request, or helper script.

## Resolve the caller identity

Use the live kotgent pane as identity by default. Never read `KOTGENT_SESSION_ID` as identity or copy it
into `--session`. Outside a kotgent pane, require an exact session ID explicitly supplied by the invocation
context or user and append `--session <session-id>` to the session-scoped commands below. Never infer an ID
from provider conversation IDs, environment variables, names, cwd, recency, or `kotgent list`. Choose one
mode for the whole run.

Require `git` and `kotgent` on `PATH` and a Git worktree, but make the pane form the first `kotgent task`
command:

```text
kotgent task show
```

Use `kotgent task show --session <session-id>` only in explicit outside-pane mode.

Interpret it strictly:

- Exit `0` means the session already holds a task. Report that task and stop; do not claim or call `next`.
- Continue only on exit `1`, empty stdout, no `status` field, and `error` exactly equal to the matching
  message: ``this session is not linked to a task — name one, or link one with `kotgent task claim <ref>` ``
  in pane mode, or `session '<session-id>' is not linked to a task — name one: kotgent task <command>
  <ref> --session <session-id>` in explicit mode.
- Treat every other response as a real failure and stop. Exit `2` is a command-construction bug whose
  stderr may be plain usage text.

Never use `task unlink` to make a session appear free.

## Resolve a candidate

When no ref was supplied:

1. Resolve the Git root, read its `.kotgent.json`, and require the exact project UUID in
   `kotgent project list`. If it is absent or archived, stop; never initialize, restore, switch, or retry.
2. Run:

   ```text
   kotgent task next --project <project-uuid>
   ```

3. Treat exit `3` with `{"task":null}` as normal absence of work and stop successfully. Treat any other
   nonzero exit as failure. Record the returned ref; do not call `next` again.

When a ref was supplied:

1. Run `kotgent task show <ref>` before claiming.
2. Require `task.state == "todo"` and `task.blocked == false`. Stop for blocked work and for
   `in_progress`, `review`, or `done`; never auto-claim those states.
3. Require the task's project UUID in `kotgent project list`. Stop if it is unknown or archived.
4. Run `kotgent task claim <ref>` exactly once.

Append `--session <session-id>` to `task next` and `task claim` only in explicit outside-pane mode.

Task links are non-exclusive. A successful claim is not proof of ownership.

## Detect parallel work after claiming

Immediately run ref-less `kotgent task show` again (with `--session` only in explicit outside-pane mode),
require its returned ref to match the claimed candidate, and inspect the refreshed task, complete activity
feed, and every linked session. Also inspect `git status --short`, the current branch or detached state,
full HEAD, and diffs relevant to the task.

Treat these as parallel-work signals unless the user already established a division of work:

- another non-archived, live linked session;
- comments or links from another session indicating active implementation;
- uncommitted changes overlapping the task that this session did not create;
- recent commits or task transitions showing someone else is already executing the same scope.

On any signal, leave one concrete coordination comment naming the sessions, paths, activity, or commits:

```text
kotgent task comment -m <coordination-evidence-and-request>
```

Append `--session <session-id>` only in explicit outside-pane mode.

Then stop with the task left `in_progress` and linked. Do not unlink it, claim another task, or race the
other worker.

If no conflict exists, immediately continue with the `work-task` workflow from this plugin, carrying the
ref, identity mode, refreshed detail, and Git snapshot forward. Do not stop after claiming and do not
claim the task again. Never run `task done`, and never run `task next` after review.
Files in this package (2)
  • SKILL.md 4 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · Heapy/kortex100Apache-2.0
restarter/lets-workflow100MIT

Database snapshot: 13.11.2026 · package version 96c4bd59c579 (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

  • 100work-task
    Execute the kotgent task linked to the current session, coordinate concurrent work, implement and verify repository changes, report meaningful progress or blockers, and submit the task for human review. Use when the user asks to work, continue, implement, finish, or resume a linked kotgent task.
  • 100make-plan
    Create or revise a structured implementation plan on a kotgent task and work through its browser review rounds. Use when the user asks to make, write, revise, or review a kotgent plan before implementation.
  • 100continue-context
    Take over the work a context file describes and drive it as the main agent. Use when the user or a resume prompt names a context file (a task context.md, the project context.md) and asks to continue, resume or take over; when a session is woken with no context by a notification;…
  • 100matrix-handoff
    Safely move the active repository and current coding-task context to the user's Matrix OS computer, then start a continuing Codex or Claude session there. Use when the user asks to continue work on Matrix, hand a local task to Matrix, upload the current project to Matrix, or…
  • 100tasks
    Create, claim, refine, advance, recover, resume, and complete collaborative komnet tasks. Use when a komnet inbox item carries task metadata, the user delegates shared work to one or any agent, an agent wants to take an open task, task state is stale, blocked, or stuck, several…
  • 100tasks
    Create, claim, refine, advance, recover, resume, and complete collaborative komnet tasks. Use when a komnet inbox item carries task metadata, the user delegates shared work to one or any agent, an agent wants to take an open task, task state is stale, blocked, or stuck, several…

Feedback and reports

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