work
- Repo stars 330
- License MIT
- Author updated Live
- Author repo claude-skill-registry
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @majiayu000 · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: work
description: Find and start the next highest-priority expedition from the kanban board Find and start work on…
category: data
runtime: no special runtime
---
# work output preview
## PART A: Task fit
- Use case: Find and start the next highest-priority expedition from the kanban board Find and start work on an expedition. If an expedition ID is provided ($ARGUMENTS), start that one. Otherwise, find the next highest-priority ready item. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Steps / 1. Check Current Work / 2. Find Ready Work” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Find and start the next highest-priority expedition from the kanban board Find and start work on an expedition. If an expedition ID is provided ($ARGUMENTS), start that one. Otherwise, find the next highest-priority ready item. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Steps / 1. Check Current Work / 2. Find Ready Work” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Steps / 1. Check Current Work / 2. Find Ready Work”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: work
description: Find and start the next highest-priority expedition from the kanban board Find and start work on…
category: data
source: majiayu000/claude-skill-registry
---
# work
## When to use
- Find and start the next highest-priority expedition from the kanban board Find and start work on an expedition. If an…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Steps / 1. Check Current Work / 2. Find Ready Work” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "work" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Steps / 1. Check Current Work / 2. Find Ready Work
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Pick Up Work
Find and start work on an expedition. If an expedition ID is provided ($ARGUMENTS), start that one. Otherwise, find the next highest-priority ready item.
Steps
1. Check Current Work
First, check if already working on something:
yurtle-kanban list --status in_progressIf items are in progress, show them and ask if the user wants to continue or pick up new work.
2. Find Ready Work
If no specific expedition requested:
yurtle-kanban list --status ready --limit 5Show the top 5 ready items with their priorities.
3. Start Work
Once an expedition is selected (either from $ARGUMENTS or user choice):
# Move to in_progress
yurtle-kanban move EXP-XXX in_progress
# Create expedition branch from main
git checkout main
git pull origin main
git checkout -b expedition/exp-XXX-short-descriptionIMPORTANT: Expedition branches use the expedition/exp-XXX-name prefix and are never deleted (permanent memory).
4. Load Context
Read the expedition file to understand the work:
# Find and read the expedition file
cat kanban-work/expeditions/EXP-XXX*.mdSummarize:
- What needs to be done (Build Steps)
- Success criteria
- Dependencies
- Current status from Ship's Log
5. Ready to Work
Confirm the expedition is loaded and ready to begin implementation.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review