Agent skill

Ogt Docs Create Task

by LeoYeAI in LeoYeAI/openclaw-master-skills

Create and manage task documents in the docs/todo/ workflow.

MITAuto-check passed

Install Ogt Docs Create Task

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill ogt-docs-create-task -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills ogt-docs-create-task --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ogt-docs-create-task .claude/skills/ogt-docs-create-task && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ogt-docs-create-task
GitHub stars
2.2k
Token cost
~5.2k tokens
SKILL.md length
442 words
Files
2
Skills in repo
1,215
Repo updated
First seen
Licence
MIT

At a glance

Create and manage task documents in the docs/todo/ workflow.

  • Works in 5 steps: Create folder:… → Create task.md with Summary, Objectives,… → Optionally add context.md for background → …
  • Creating new tasks
  • SKILL.md covers Overview, Folder Structure, Stage: pending/ and Stage: in_progress/, plus 8 more sections
  • Reaches github.com and lucaong.github.io

What it does

Ogt Docs Create Task is an agent skill from LeoYeAI/openclaw-master-skills. Create and manage task documents in the docs/todo/ workflow. Use when creating new tasks, updating task status, or moving tasks between workflow stages. Provides complete task lifecycle management with verification.

Its SKILL.md is about 5.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).

The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Creating new tasks
  • Updating task status
  • Moving tasks between workflow stages

Example prompts

  • “/ogt-docs-create-task”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Create folder: docs/todo/pending/{task_slug}/
  2. Create task.md with Summary, Objectives, Acceptance Criteria
  3. Optionally add context.md for background
  4. Create .priority with level (critical/high/medium/low)
  5. Create .version with schema version

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown, bash, mermaid, json and typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com
    • lucaong.github.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ogt Docs Create Task loads about 5.2k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 442 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~5.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 442 words, ~5,165 tokens.

Download SKILL.mdSave it as .claude/skills/ogt-docs-create-task/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
ogt-docs-create-task
description
Create and manage task documents in the docs/todo/ workflow. Use when creating new tasks, updating task status, or moving tasks between workflow stages. Provides complete task lifecycle management with verification.

OGT Docs - Create Task

Complete guide for creating and managing tasks in the docs-first workflow.

Overview

Tasks are the unit of work in the docs-first system. Each task is a folder that moves through workflow stages, accumulating documentation and signals as it progresses.

mermaid
flowchart LR
    subgraph stages ["Task Lifecycle"]
        P[pending] --> IP[in_progress]
        IP --> R[review]
        R --> D[done]

        IP --> B[blocked]
        B --> IP

        R --> REJ[rejected]
        REJ --> P

        D --> IMP[implemented]
    end

    style P fill:#fef3c7
    style IP fill:#dbeafe
    style R fill:#e0e7ff
    style B fill:#fee2e2
    style REJ fill:#fecaca
    style D fill:#d1fae5
    style IMP fill:#a7f3d0

Folder Structure

docs/todo/
├── pending/                    # Tasks not yet started
│   └── {task_slug}/
│       ├── task.md             # Primary task definition
│       ├── context.md          # Background information (optional)
│       ├── .version            # Schema version
│       └── .priority           # Priority level (content: critical|high|medium|low)
│
├── in_progress/                # Tasks being actively worked on
│   └── {task_slug}/
│       ├── task.md
│       ├── progress.md         # Work log and updates
│       ├── .version
│       ├── .priority
│       ├── .assigned_to_{agent}  # Who's working on it
│       └── .started_at         # Timestamp when started
│
├── review/                     # Tasks awaiting review
│   └── {task_slug}/
│       ├── task.md
│       ├── progress.md
│       ├── implementation.md   # What was done
│       ├── .version
│       ├── .ready_for_review   # Empty signal
│       ├── .pr_link            # PR URL if applicable
│       └── .review_requested_at
│
├── blocked/                    # Tasks that cannot proceed
│   └── {task_slug}/
│       ├── task.md
│       ├── progress.md
│       ├── .version
│       ├── .blocked            # Empty signal
│       ├── .blocked_reason     # Why blocked (content)
│       ├── .blocked_at         # When blocked
│       └── .depends_on         # What it's waiting for
│
├── done/                       # Completed and verified tasks
│   └── {task_slug}/
│       ├── task.md
│       ├── progress.md
│       ├── implementation.md
│       ├── verification.md     # How it was verified
│       ├── .version
│       ├── .verified           # Empty signal - REQUIRED
│       ├── .completed_at       # Completion timestamp
│       └── .verified_by_{agent}  # Who verified
│
├── rejected/                   # Tasks that were declined
│   └── {task_slug}/
│       ├── task.md
│       ├── .version
│       ├── .rejected           # Empty signal
│       ├── .rejected_reason    # Why rejected (content)
│       └── .rejected_at        # When rejected
│
└── implemented/                # Done tasks that are deployed/released
    └── {task_slug}/
        ├── task.md
        ├── implementation.md
        ├── verification.md
        ├── .version
        ├── .verified
        ├── .completed_at
        ├── .implemented_at     # When deployed
        └── .release_version    # Which release included it

Stage: pending/

Tasks that are defined but not yet started.

pending/
└── fuzzy_search/
    ├── task.md
    ├── context.md
    ├── .version
    └── .priority
task.md
markdown
# Task: Fuzzy Search Implementation

## Summary

Replace substring search with fuzzy indexed search using MiniSearch.

## Objectives

- Install MiniSearch library
- Create SearchIndexService
- Refactor GlobalSearch component
- Add debounce to search input

## Acceptance Criteria

- [ ] Typing "fir" returns "Fireball", "Fire Elemental", etc.
- [ ] Results ranked by relevance
- [ ] Search responds within 16ms
- [ ] TypeScript compiles clean

## Dependencies

- None

## Estimated Effort

Medium (2-4 hours)

## References

- MiniSearch docs: https://lucaong.github.io/minisearch/
- Current search: front/components/features/GlobalSearch.tsx
context.md
markdown
# Context: Fuzzy Search

## Current State

GlobalSearch.tsx uses `String.toLowerCase().includes()` for matching.
No ranking, no debounce, no fuzzy matching.

## User Request

"Global search with ctrl+k, should be instant, indexed, fuzzy.
If I search fire just by typing fir I should get instantly a list."

## Technical Decision

MiniSearch chosen over:

- Fuse.js (heavier, slower on large datasets)
- Lunr (no fuzzy matching)

MiniSearch is 6KB gzipped, used by VitePress.
.version
json
{ "schema": "1.0", "created": "2026-02-05T10:00:00Z" }
.priority
high

Stage: in_progress/

Tasks actively being worked on.

Example: in_progress/card_variants/
in_progress/
└── card_variants/
    ├── task.md
    ├── progress.md
    ├── .version
    ├── .priority
    ├── .assigned_to_claude
    └── .started_at
task.md
markdown
# Task: Card Variant System Expansion

## Summary

Add Condensed, ListItemCondensed, and stub Quaternary/Penta card variants.

## Objectives

- Update UICardFrameType enum
- Create \*Condensed.tsx components
- Create \*ListItemCondensed.tsx components
- Stub Quaternary and Penta variants
- Update all \*CardMain.tsx orchestrators

## Acceptance Criteria

- [ ] Condensed renders 48-64px tile with art, border, icon badge
- [ ] ListItemCondensed renders 32px single-line row
- [ ] Quaternary/Penta exist as stubs
- [ ] All orchestrators route to new variants
- [ ] TypeScript compiles clean

## Dependencies

- None

## Estimated Effort

Large (4-8 hours)
progress.md
markdown
# Progress: Card Variants

## 2026-02-05 10:30 - Started

- Read existing card components
- Identified 8 entity types needing variants
- Created implementation plan

## 2026-02-05 11:00 - UICardFrameType Updated

- Added Condensed, Penta, ListItem, ListItemCondensed to type
- File: front/data/app-generics.ts:82

## 2026-02-05 11:30 - CreatureCardCondensed Created

- Created front/components/compendium/CreatureCardCondensed.tsx
- 64x64 portrait, rarity border, type icon badge
- Tooltip on hover shows name

## Current Status

- [x] Type definition updated
- [x] CreatureCardCondensed
- [ ] ItemCardCondensed
- [ ] AbilityCardCondensed
- [ ] Remaining entity types
- [ ] ListItemCondensed variants
- [ ] Quaternary/Penta stubs
- [ ] Orchestrator updates
.assigned_to_claude
(empty file - presence indicates assignment)
.started_at
2026-02-05T10:30:00Z

Stage: review/

Tasks completed and awaiting review.

Example: review/spell_routes/
review/
└── spell_routes/
    ├── task.md
    ├── progress.md
    ├── implementation.md
    ├── .version
    ├── .ready_for_review
    ├── .pr_link
    └── .review_requested_at
task.md
markdown
# Task: Wire SpellDetailView into Router

## Summary

SpellDetailView.tsx exists but is not routed. Wire it into the app router.

## Objectives

- Add route to APP_ROUTES
- Add Route element in App.tsx
- Verify component loads correctly

## Acceptance Criteria

- [ ] /spells/:slug route works
- [ ] SpellDetailView renders with spell data
- [ ] Navigation from spell cards works
- [ ] TypeScript compiles clean
progress.md
markdown
# Progress: Spell Routes

## 2026-02-05 09:00 - Started

- Located SpellDetailView at front/app/(main)/compendium/SpellDetailView.tsx
- Reviewed existing route patterns

## 2026-02-05 09:15 - Implementation Complete

- Added spell_detail to APP_ROUTES in app-configs.ts
- Added Route element in App.tsx
- Tested with /spells/fireball - works
- TypeScript compiles clean
implementation.md
markdown
# Implementation: Spell Routes

## Files Changed

### front/data/app-configs.ts

Added route configuration:

```typescript
spell_detail: {
  path: '/spells/:slug',
  label: 'Spell Detail',
}
```
front/app/App.tsx

Added import and route:

typescript
import SpellDetailView from './(main)/compendium/SpellDetailView';
// ...
<Route path="/spells/:slug" element={<SpellDetailView />} />

Testing

  • Manual test: /spells/fireball loads correctly
  • Manual test: /spells/magic-missile loads correctly
  • TypeScript: No errors

#### .ready_for_review

(empty file)


#### .pr_link

https://github.com/org/repo/pull/123


#### .review_requested_at

2026-02-05T09:30:00Z


---

## Stage: blocked/

Tasks that cannot proceed due to dependencies or blockers.

### Example: blocked/auth_refactor/

blocked/ └── auth_refactor/ ├── task.md ├── progress.md ├── .version ├── .blocked ├── .blocked_reason ├── .blocked_at └── .depends_on


#### task.md
```markdown
# Task: Auth Service Refactor

## Summary
Refactor AuthService to support multiple OAuth providers.

## Objectives
- Abstract provider-specific logic
- Add Steam OAuth support
- Implement token refresh flow
- Update all auth consumers

## Acceptance Criteria
- [ ] Google OAuth still works
- [ ] Discord OAuth still works
- [ ] Steam OAuth works
- [ ] Token refresh is automatic
- [ ] No breaking changes to API
progress.md
markdown
# Progress: Auth Refactor

## 2026-02-03 14:00 - Started

- Analyzed current AuthService implementation
- Identified 3 provider-specific code paths

## 2026-02-03 15:00 - BLOCKED

- Steam OAuth requires server-side changes
- Backend team needs to add Steam provider to Strapi
- Cannot proceed until backend work is complete

## Waiting For

- Backend task: "Add Steam OAuth Provider to Strapi"
- ETA: Unknown
.blocked
(empty file)
.blocked_reason
Requires backend changes: Steam OAuth provider must be added to Strapi before frontend can implement Steam login flow. Backend task not yet created.
.blocked_at
2026-02-03T15:00:00Z
.depends_on
- backend/steam_oauth_provider (not yet created)
- Strapi plugin configuration

Stage: done/

Completed tasks that have been verified.

Example: done/ogt_cli_commands/
done/
└── ogt_cli_commands/
    ├── task.md
    ├── progress.md
    ├── implementation.md
    ├── verification.md
    ├── .version
    ├── .verified
    ├── .completed_at
    └── .verified_by_claude
task.md
markdown
# Task: OGT CLI Check Commands

## Summary

Create generic file/data validation CLI tools under `ogt check`.

## Objectives

- ogt check assets - Check for missing files
- ogt check slugs - Verify slug conventions
- ogt check indexed - Verify index.ts exports
- ogt check data - Validate against schema

## Acceptance Criteria

- [x] All commands have --help
- [x] Commands return proper exit codes
- [x] JSON output option available
- [x] TypeScript compiles clean
verification.md
markdown
# Verification: OGT CLI Commands

## Verification Date

2026-01-30

## Tests Performed

### Command Existence

```bash
$ ogt check --help
# ✅ Shows subcommands: assets, slugs, indexed, data, from-list

$ ogt check assets --help
# ✅ Shows usage and flags

$ ogt check slugs --help
# ✅ Shows usage and flags

$ ogt check indexed --help
# ✅ Shows usage and flags

$ ogt check data --help
# ✅ Shows usage and flags
```
Functional Tests
bash
$ ogt check indexed creatures
# ✅ Returns JSON with 197 total, 197 passed

$ ogt check slugs front/data/app-creatures -r
# ✅ Returns JSON with slug validation results

$ ogt check assets static/public/creatures portrait.png -r
# ✅ Returns JSON listing missing portraits
Exit Codes
bash
$ ogt check indexed creatures && echo "pass"
# ✅ Exits 0, prints "pass"

$ ogt check indexed nonexistent || echo "fail"
# ✅ Exits 1, prints "fail"

Verification Result

PASS - All acceptance criteria met


#### .verified

(empty file - REQUIRED for done/ status)


#### .completed_at

2026-01-30T14:00:00Z


#### .verified_by_claude

(empty file)


---

## Stage: rejected/

Tasks that were declined and will not be implemented.

### Example: rejected/legacy_api_compat/

rejected/ └── legacy_api_compat/ ├── task.md ├── .version ├── .rejected ├── .rejected_reason └── .rejected_at


#### task.md
```markdown
# Task: Legacy API Compatibility Layer

## Summary
Create compatibility layer for v0 API endpoints.

## Objectives
- Map v0 endpoints to v1 services
- Maintain backward compatibility for 6 months
- Log deprecation warnings

## Acceptance Criteria
- [ ] All v0 endpoints work
- [ ] Deprecation headers sent
- [ ] Usage logging enabled
.rejected
(empty file)
.rejected_reason
Decision: Clean break over compatibility layer.

Rationale:
1. No external consumers of v0 API
2. Maintenance burden outweighs benefits
3. v0 endpoints have security issues
4. Better to document migration path

Alternative: Create migration guide instead.
See: docs/guides/v0_to_v1_migration/
.rejected_at
2026-02-01T09:00:00Z

Stage: implemented/

Tasks that are done AND deployed/released to production.

Example: implemented/creatures_index/
implemented/
└── creatures_index/
    ├── task.md
    ├── implementation.md
    ├── verification.md
    ├── .version
    ├── .verified
    ├── .completed_at
    ├── .implemented_at
    └── .release_version
.implemented_at
2026-02-02T10:00:00Z
.release_version
v1.2.0

Task Lifecycle Operations

Creating a New Task
mermaid
flowchart TD
    A[User Request] --> B{Task Defined?}
    B -->|No| C[Create task.md]
    C --> D[Add context.md if needed]
    D --> E[Set .priority]
    E --> F[Add .version]
    F --> G[Place in pending/]
    B -->|Yes| H[Update existing task]

Steps:

  1. Create folder: docs/todo/pending/{task_slug}/
  2. Create task.md with Summary, Objectives, Acceptance Criteria
  3. Optionally add context.md for background
  4. Create .priority with level (critical/high/medium/low)
  5. Create .version with schema version
Starting a Task
bash
# Move from pending to in_progress
mv docs/todo/pending/{task_slug} docs/todo/in_progress/

# Add assignment signal
touch docs/todo/in_progress/{task_slug}/.assigned_to_{agent}

# Add start timestamp
echo "$(date -Iseconds)" > docs/todo/in_progress/{task_slug}/.started_at

# Create progress log
touch docs/todo/in_progress/{task_slug}/progress.md
Blocking a Task
bash
# Move to blocked
mv docs/todo/in_progress/{task_slug} docs/todo/blocked/

# Add blocked signals
touch docs/todo/blocked/{task_slug}/.blocked
echo "Reason here" > docs/todo/blocked/{task_slug}/.blocked_reason
echo "$(date -Iseconds)" > docs/todo/blocked/{task_slug}/.blocked_at
Submitting for Review
bash
# Move to review
mv docs/todo/in_progress/{task_slug} docs/todo/review/

# Add review signals
touch docs/todo/review/{task_slug}/.ready_for_review
echo "$(date -Iseconds)" > docs/todo/review/{task_slug}/.review_requested_at

# Add implementation docs
# Create implementation.md documenting what was done
Completing a Task

CRITICAL: Must verify before marking done!

bash
# 1. Run ALL acceptance criteria checks
# 2. Document in verification.md
# 3. ONLY if all pass:

# Move to done
mv docs/todo/review/{task_slug} docs/todo/done/

# Add completion signals
touch docs/todo/done/{task_slug}/.verified  # REQUIRED
echo "$(date -Iseconds)" > docs/todo/done/{task_slug}/.completed_at
touch docs/todo/done/{task_slug}/.verified_by_{agent}
Rejecting a Task
bash
# Move to rejected
mv docs/todo/review/{task_slug} docs/todo/rejected/

# Add rejection signals
touch docs/todo/rejected/{task_slug}/.rejected
echo "Reason here" > docs/todo/rejected/{task_slug}/.rejected_reason
echo "$(date -Iseconds)" > docs/todo/rejected/{task_slug}/.rejected_at

Signal Files Reference

Status Signals (empty files)
SignalStageMeaning
.blockedblocked/Task cannot proceed
.ready_for_reviewreview/Ready for review
.verifieddone/, implemented/REQUIRED - Implementation verified
.rejectedrejected/Task declined
Show full SKILL.md (174 more words)Show less
Assignment Signals (empty files)
SignalStageMeaning
.assigned_to_{agent}in_progress/Who's working on it
.verified_by_{agent}done/Who verified it
.approved_by_{name}anyWho approved
Content Signals (contain text)
SignalContentExample
.versionJSON schema version{"schema": "1.0", "created": "..."}
.priorityPriority levelhigh
.blocked_reasonWhy blockedFree text explanation
.rejected_reasonWhy rejectedFree text explanation
.depends_onDependenciesList of dependencies
.pr_linkPR URLhttps://github.com/...
.started_atISO timestamp2026-02-05T10:00:00Z
.completed_atISO timestamp2026-02-05T14:00:00Z
.blocked_atISO timestamp2026-02-05T12:00:00Z
.rejected_atISO timestamp2026-02-05T09:00:00Z
.implemented_atISO timestamp2026-02-05T16:00:00Z
.release_versionVersion stringv1.2.0

Task.md Template

markdown
# Task: {Title}

## Summary

One paragraph describing what needs to be done and why.

## Objectives

- Specific objective 1
- Specific objective 2
- Specific objective 3

## Acceptance Criteria

- [ ] Verifiable criterion 1
- [ ] Verifiable criterion 2
- [ ] Verifiable criterion 3
- [ ] TypeScript compiles clean (if applicable)

## Dependencies

- {dependency} or "None"

## Estimated Effort

{Tiny|Small|Medium|Large|XLarge} ({time estimate})

## References

- Relevant link 1
- Relevant file path
- Related task

Verification Rules

NEVER mark a task as done without verification.

Verification Checklist
markdown
## For each acceptance criterion:

1. IDENTIFY: What command/action proves this criterion?
2. RUN: Execute the verification
3. CAPTURE: Record the output
4. ASSESS: Does it pass?

## Required Verifications by Type:

### File Creation

- [ ] File exists: `test -f {path} && echo "EXISTS"`
- [ ] File is exported (if module): `grep "export" {index_file}`

### Dependency Installation

- [ ] In package.json: `grep "{package}" package.json`
- [ ] Can import: Create test file with import

### Route Addition

- [ ] In router: `grep "{route}" {router_file}`
- [ ] Navigable: Test in browser

### Pattern Removal

- [ ] Zero matches: `grep -r "{pattern}" {path} | wc -l` = 0

### Type Addition

- [ ] Type exists: `grep "type {Name}" {types_file}`
- [ ] Compiles: `tsc --noEmit` or equivalent

### General

- [ ] TypeScript compiles: Run type checker
- [ ] Tests pass: Run test suite
- [ ] No console errors: Check browser/runtime

Common Mistakes

MistakeWhy It's WrongCorrect Approach
Moving to done/ without .verifiedNo proof of completionVerify first, then move
Trusting task.md checkboxesCheckboxes can be wrongRun actual verification
Skipping implementation.mdNo record of what changedDocument all changes
Empty verification.mdNo proof of verificationRecord actual test output
Multiple tasks in progressContext switching wasteFinish one, then start next
Editing task.md in done/History should be immutableCreate follow-up task instead

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/ogt-docs-create-task of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Ogt Docs Create Task next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ogt Docs Create Task compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ogt Docs Create Task this skillLeoYeAI/openclaw-master-skills2.2k—~5.2kAutomated safety check: PassMIT
Todopoteto/noodle420—~382Automated safety check: PassMIT
TodoPatrickSUDO/fadacai-portfolio142—~1.5kAutomated safety check: PassMIT
Todoploxc/modbux108—~898Automated safety check: PassMIT
Todo Writenexu-io/open-design100k—~225Automated safety check: PassApache-2.0
Dingtalk TodoDingTalk-Real-AI/dingtalk-workspace-cli3.2k—~1.9kAutomated safety check: PassApache-2.0

Similar skills

  • Todo

    poteto/noodle

    Add, complete, or view items in the brain/todos.md backlog. An agent skill from poteto/noodle.

    420 GitHub stars~382 tokensUpdated 6 mo ago
    Agent WorkflowsAuto-check passed
  • Todo

    PatrickSUDO/fadacai-portfolio

    生成下一個交易日的優先行動清單。當用戶問「明天開盤要做什麼」、「今天要操作什麼」、「給我待辦」、「接下來要做什麼」、「有什麼需要處理」等問題時立刻使用此 skill。也適用於盤中(「現在有什麼要做」)和盤後(「今天還有什麼沒做」)場景。不要等用戶說 /todo 才觸發,只要問的是「下一步行動」的問題就應該用。

    142 GitHub stars~1.5k tokensUpdated today
    Business, Finance & HRAuto-check passed
  • Todo

    ploxc/modbux

    Route something you want to record to the place that holds it — TODO.md, a GitHub issue, the memory directory, or the plan in flight.

    108 GitHub stars~898 tokensUpdated today
    DevelopmentAuto-check passed
  • Todo Write

    nexu-io/open-design

    TodoWrite-driven plan that the agent commits to before generation.

    100k GitHub stars~225 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Dingtalk Todo

    DingTalk-Real-AI/dingtalk-workspace-cli

    钉钉待办 / TODO。Use when 用户说 创建待办/TODO/任务提醒/指派任务/标记完成/查待办/紧急待办/循环待办/批量建待办/逾期待办。不做日报周报(走 dingtalk-misc)、审批(走 dingtalk-misc)、日程(走 dingtalk-calendar)。命令前缀:dws todo。

    3.2k GitHub stars~1.9k tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed
  • Todo Manager

    huangruiteng/CS-Notes

    Todo 管理 - 管理 CS-Notes 项目中的 todo 任务,包括任务创建、状态更新、优先级管理等功能. An agent skill from huangruiteng/CS-Notes.

    4k GitHub stars~165 tokensUpdated yesterday
    Auto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,215 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Ogt Docs Create Task

What does Ogt Docs Create Task do?

Create and manage task documents in the docs/todo/ workflow. Ogt Docs Create Task is an agent skill from LeoYeAI/openclaw-master-skills. Create and manage task documents in the docs/todo/ workflow.

When should I use Ogt Docs Create Task?

Ogt Docs Create Task fits situations like: creating new tasks; updating task status; moving tasks between workflow stages.

How do I install Ogt Docs Create Task in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill ogt-docs-create-task -a claude-code`. Or copy the skill folder (skills/ogt-docs-create-task in LeoYeAI/openclaw-master-skills) into .claude/skills/ogt-docs-create-task in your project. Claude Code loads it when a task matches its description.

How do I install Ogt Docs Create Task in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill ogt-docs-create-task -a codex`. Or copy the skill folder (skills/ogt-docs-create-task in LeoYeAI/openclaw-master-skills) into .agents/skills/ogt-docs-create-task in your project. Codex loads it when a task matches its description.

Can I use Ogt Docs Create Task in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill ogt-docs-create-task -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ogt-docs-create-task, .gemini/skills/ogt-docs-create-task, .github/skills/ogt-docs-create-task and .opencode/skills/ogt-docs-create-task in your project.

What does Ogt Docs Create Task need to run?

SKILL.md names no scripts, command-line tools or credentials: Ogt Docs Create Task is instructions for the agent only.

Does Ogt Docs Create Task access the network?

SKILL.md names 2 domains. In commands or code: github.com and lucaong.github.io; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Ogt Docs Create Task safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ogt Docs Create Task use?

Ogt Docs Create Task is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ogt Docs Create Task use?

About 5.2k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ogt Docs Create Task?

Skills that share tags, products or a category with Ogt Docs Create Task: Todo (poteto/noodle, 420 stars), Todo (PatrickSUDO/fadacai-portfolio, 142 stars), Todo (ploxc/modbux, 108 stars) and Todo Write (nexu-io/open-design, 100k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ogt Docs Create Task?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,158 GitHub stars. The repository holds 1,215 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.