โ† All skills
Tencent SkillHub ยท Productivity

ERPClaw-Projects

Project management, tasks, milestones, and timesheets for ERPClaw

skill openclawclawhub Free
0 Downloads
0 Stars
0 Installs
0 Score
High Signal

Project management, tasks, milestones, and timesheets for ERPClaw

โฌ‡ 0 downloads โ˜… 0 stars Unverified but indexed

Install for OpenClaw

Quick setup
  1. Download the package from Yavira.
  2. Extract the archive and review SKILL.md first.
  3. Import or place the package into your OpenClaw setup.

Requirements

Target platform
OpenClaw
Install method
Manual import
Extraction
Extract archive
Prerequisites
OpenClaw
Primary doc
SKILL.md

Package facts

Download mode
Yavira redirect
Package format
ZIP package
Source platform
Tencent SkillHub
What's included
SKILL.md

Validation

  • Use the Yavira download entry.
  • Review SKILL.md after the package is downloaded.
  • Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

  1. Download the package from Yavira.
  2. Extract it into a folder your agent can access.
  3. Paste one of the prompts below and point your agent at the extracted folder.
New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Trust & source

Release facts

Source
Tencent SkillHub
Verification
Indexed source record
Version
1.0.0

Documentation

ClawHub primary doc Primary doc: SKILL.md 18 sections Open source page

Core Behavior

User mentions a project โ†’ help define scope, create folder User adds tasks โ†’ capture in project context Regular review prompts โ†’ surface stalled projects Create ~/projects/ as workspace

First Question

"What does done look like?" โ€” define success before starting Scope creep is the project killer โ€” clear boundaries from day one If they can't define done, the project isn't ready to start

Project Types to Recognize

One-time goal: clear end state, then archive (move apartments, plan trip) Ongoing area: never truly done, maintain indefinitely (health, career) Client work: external deadline, deliverables, often paid Learning: skill acquisition, may spawn other projects Creative: writing, art, building โ€” process matters as much as output

Minimal Project Structure

Folder with project name: ~/projects/kitchen-renovation/ README.md: what, why, done criteria, deadline if any tasks.md: simple checklist, add as discovered notes.md: decisions made, research, reference material

When User Starts a Project

Ask: "What's the one sentence description?" Ask: "When does this need to be done?" (or "no deadline") Ask: "What's the very next physical action?" Create folder with README containing answers

Task Capture

Quick capture: "Add to kitchen project: call contractor" Tasks are concrete actions, not vague goals "Research options" is a task, "figure out renovation" is not Estimate size if useful: small/medium/large or hours

When Projects Grow

More than 15 tasks โ†’ consider grouping into phases Multiple workstreams โ†’ split into areas within project Dependencies emerging โ†’ note which tasks block others Collaborators involved โ†’ note who owns what

Phase/Milestone Structure

For larger projects: ~/projects/kitchen-renovation/ โ”œโ”€โ”€ README.md โ”œโ”€โ”€ phase-1-planning/ โ”‚ โ”œโ”€โ”€ tasks.md โ”‚ โ””โ”€โ”€ notes.md โ”œโ”€โ”€ phase-2-demo/ โ”œโ”€โ”€ phase-3-install/ โ””โ”€โ”€ archive/

Active Project Limits

Suggest maximum 3-5 active projects โ€” more means nothing progresses Distinguish active (working this week) from someday (parked intentionally) Parked projects go in ~/projects/_someday/ Review someday quarterly โ€” activate, archive, or delete

Weekly Project Review

What progressed this week? What's the next action for each active project? Any projects stalled more than 2 weeks? Any someday projects ready to activate?

Stalled Project Detection

No task completions in 2+ weeks โ†’ surface in review Ask: "Is this still a priority? Block or drop?" Options: push forward, park to someday, kill it Killing projects is healthy โ€” better than zombie projects

Project Completion

Define done checklist in README from start When complete: review what went well, what didn't Archive to ~/projects/_archive/year/ Celebrate completion โ€” don't just move to next thing

Client/Work Projects

Add: deadline, contact info, rate if applicable Track time if billing: simple log in project folder Deliverables list with status Communication log: key decisions and approvals

What NOT To Suggest

Complex project management app until files fail Rigid methodology (Agile, GTD, etc.) โ€” adapt to user Gantt charts for personal projects โ€” overkill Time tracking for non-billable work โ€” adds friction

Project Templates

Offer to create templates for recurring project types: "You start client projects often โ€” want a template?" Template: folder structure, README prompts, standard tasks Keep templates minimal โ€” adapt per project

Integration Points

Calendar: deadlines, milestones Contacts: collaborators, stakeholders Invoices: if client project with billing Goals: projects often serve larger goals

Someday/Maybe List

Ideas not ready for commitment Review monthly โ€” promote, delete, or keep parking No guilt about long lists โ€” it's a holding pen "This would be cool but not now" is valid

Project Metrics (When Asked)

How long did similar projects take? Completion rate: started vs finished Average project duration Don't track obsessively โ€” only if user finds it useful

Category context

Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package
1 Docs
  • SKILL.md Primary doc