agentsclimarketplace

Task

Skill lsnackerman/raw-clauding-skills/task

Create a living task doc from natural language. Use when you want to track work, capture a new project, or create a thinking log that accumulates context across sessions.From its SKILL.md

Install
npx -y skills add lsnackerman/raw-clauding-skills --skill task

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

SKILL.md

2.7 KB, 572 tokens by cl100k_base, as published. Nobody here has run it

/task - Create a Living Task Doc

Create a task doc from natural language. A thinking log that accumulates context, decisions, and observations over time.


What To Do

  1. Parse the request — understand what work is being described
  2. Figure out metadata — topic, tags, priority
  3. Write the file — with the structure below
  4. Note the connection — this doc is where /wrap updates and /sync captures link back to

Task Doc Structure

---
tags: [{tag1}, {tag2}]
priority: {P0|P1|P2|P3}
status: todo
created_date: {YYYY-MM-DD}
---

# {Title}

## WHAT

{Description — why this matters, context, what triggered this}

---

## WHO

{People involved — names, roles, current status}

---

## HOW

### Pending (Execute Next)
- [ ] {First action item}

### Completed (Append in order of completion)
<!-- Move items here when done — newest at bottom -->

---

## OBSERVATIONS (Cumulative)

*Patterns, friction, questions worth keeping — from you or your AI*

<!-- Add observations as they emerge across sessions -->

---

## SESSION INDEX

<!-- Pointers to captured sessions related to this work -->
<!-- Format: **Session N (YYYY-MM-DD)**: [filename] — one-liner of what happened -->

---

Why This Structure

Most task trackers give you a title and a checkbox. This gives you a thinking log.

  • WHAT isn't just a description — it's the WHY that keeps you oriented when you pick this up days later
  • HOW splits pending from completed so you always know where you left off
  • OBSERVATIONS is where the real value accumulates — patterns you noticed, friction you hit, questions that emerged
  • SESSION INDEX links to your captured sessions so you can trace how the thinking evolved

When a Task Is Done

Archive completed tasks to tasks/_done/ to preserve the thinking. The task doc is a record of how you got somewhere — decisions, dead ends, observations. That's worth keeping even after the work is finished. /wrap handles this when you mark a task done.


Skill Check (After Every Task Creation)

Quick scan: anything about this task creation that felt off or could be smoother?

  • Was the WHAT section clear enough for future you?
  • Did the structure feel right for this type of work?
  • Was anything missing that you'd want next time you pick this up?

If yes → update this skill now. The improvement compounds.

If no → move on. Not every task teaches something.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.