Skills Guide

Pick Up API Task from Coordinator

VerifiedCaution

Accept an API-layer plan from the coordinator, implement it following conventions and contracts, then verify with build and tests.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
7/23/2026
Claude Code
#api#git-workflow#dotnet#kanban#clean-architecture

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Accepts an API-layer-scoped implementation plan from a coordinator and carries it through: Git branch, code, build/test, curl artifact, and completion report.

Strengths

  • Enforces strict Git hygiene: reuse or create a feature/fix branch and never commit to main
  • Requires real verification with dotnet build and dotnet test on the solution before committing
  • Generates curl commands for every new or modified endpoint as a reproducible test artifact
  • Records completion in the plan file (date, branch, build/test result, file counts, open items) and moves the Kanban card

Limitations

  • Assumes a specific repo layout (patient-care-api.sln, sibling ../patient-care-super/_contracts) and won't work as-is elsewhere
  • Depends on an internal Kanban service reachable at http://openclaw:8082/api/move
  • Explicitly restricted to the API layer; frontend or cross-cutting steps are out of scope
When to use it

When a coordinator hands you a pre-scoped plan whose steps only touch the API layer of a .NET project.

When not to use it

For non-API work, in a repo lacking this contracts/planning structure, or when the referenced Kanban service is unreachable.

Security analysis

Caution
Quality score86/100

The skill is a normal development workflow: reads project conventions, creates feature branches, runs dotnet build/test, commits, and updates planning files. It does use powerful tools (git, curl, dotnet) and makes an internal HTTP request, but there is no destructive command, secret exfiltration, obfuscation, or safety-disabling behavior. It is appropriately rated caution rather than risky.

Findings
  • •Uses network access via curl POST to an internal Kanban service (http://openclaw:8082/api/move).
  • •Performs git branch creation/commits and file moves under planning directories; legitimate but repo-modifying.
  • •No explicit allowed-tools declaration, so execution permissions rely on host defaults.
How this analysis is made

Examples

Implement an inline API plan
Pick up this API-layer plan and implement it: add a GET /patients/{id}/vitals endpoint returning a VitalDto list, following the existing Clean Architecture patterns. Create a feature branch, run build and tests, and give me the curl commands.
Pick up plan from file
Pickup the task in ../patient-care-super/planning/active/patient-vitals-api.md — move the Kanban card to DOING, implement only the API steps, verify with dotnet build and dotnet test, then append the completion block to the plan.
Complete and archive plan
Finish the remaining API steps of the active plan, record verification results, and if no other layers are pending move the plan to completed/ and add it to archive.md.

name: pickup-task description: Accept and implement an API-layer plan from the coordinator user-invocable: true

Pickup Task from Coordinator

You are receiving a plan scoped to the API layer.

Steps

  1. Read the plan. User provides it inline or as a file path.
  2. Review conventions. Re-read CLAUDE.md (Clean Architecture, DI, DTO naming).
  3. Check contracts. Read ../patient-care-super/_contracts/ for API shapes to match.
  4. Check for existing branch: git branch -a | grep -E "feature/|fix/" — reuse if one exists.
  5. Create branch if needed: feature/<desc> or fix/<desc>. Never commit to main.
  6. Kanban — Move related card to DOING: 
    curl -s --max-time 2 -X POST http://openclaw:8082/api/move \
  -H "Content-Type: application/json" -d '{"cardId": <ID>, "columnId": 4}'
  7. Implement. Only API-layer steps. Follow existing patterns when referenced.
  8. Verify: 
    dotnet build patient-care-api.sln
dotnet test patient-care-api.sln
  9. Test artifact: Produce curl commands for each new/modified endpoint.
  10. Commit with a clear message.
  11. Record completion. Append to the plan file in ../patient-care-super/planning/active/: 
    ## Completion — API
- **Date**: YYYY-MM-DD
- **Branch**: `feature/branch-name`
- **Verification**: build: PASS/FAIL | test: PASS/FAIL
- **Files**: N created, M modified
- **Test artifact**: [curl commands]
- **Open items**: None
    If other layers pending, leave in active/. If all done, move to completed/ + add to archive.md (uncommitted).
  12. Report back. Summarize implementation, verification, and open questions.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/pick-up-api-task-from-coordinator-mrx3xwii/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/pick-up-api-task-from-coordinator-mrx3xwii' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/pick-up-api-task-from-coordinator-mrx3xwii/download' --output '.skill-downloads/pick-up-api-task-from-coordinator-mrx3xwii/SKILL.md.part' && mv '.skill-downloads/pick-up-api-task-from-coordinator-mrx3xwii/SKILL.md.part' '.skill-downloads/pick-up-api-task-from-coordinator-mrx3xwii/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/pick-up-api-task-from-coordinator-mrx3xwii/SKILL.md' && test -s '.skill-downloads/pick-up-api-task-from-coordinator-mrx3xwii/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pickup-task' && cp -R '.skill-downloads/pick-up-api-task-from-coordinator-mrx3xwii' '.claude/skills/pickup-task'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/pick-up-api-task-from-coordinator-mrx3xwii'

openskills read 'pick-up-api-task-from-coordinator-mrx3xwii'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/pick-up-api-task-from-coordinator-mrx3xwii/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot