← Back to Skills Marketplace
zvirb

Backlog Grooming

by zvirb · GitHub ↗ · v1.0.2 · MIT-0
cross-platform ⚠ suspicious
85
Downloads
0
Stars
1
Active Installs
3
Versions
Install in OpenClaw
/install backlog-grooming
Description
Workflow-driven skill that autonomously manages stale items in Google Tasks.
README (SKILL.md)

\r

Lean Philosophy (Principles)\r

  • Kaizen (改善): This skill is an atomic node, broken down into its simplest, smallest component to eliminate waste and ensure perfection.\r
  • Standardized Work (Hyojun Sagyo): This node represents the most efficient, standardized path for this specific task before automation.\r
  • Jidoka (自働化): This node includes autonomous defect detection. It will stop immediately and report if it cannot achieve the expected outcome.\r \r

Backlog Grooming\r

\r This skill directs the agent to trigger the native programmatic backlog grooming plugin to maintain a clean workspace.\r \r

Cognitive Directives\r

WHEN [Triggered by schedule or user request to groom backlog] \r THEN [\r Execute the following Jidoka-validated loop:\r

  1. Execute Node: Execute the workflow_backlog_grooming plugin tool with empty JSON {} to trigger the grooming process.\r
  2. Verification Step (Jidoka): Check if the tool returns a valid JSON response with {"success": true} or an error message. IF it returns an error or hallucinated output, report the error, wait 3 seconds, and retry (max 3 times). IF it still fails, stop and notify the user.\r ]\r

Expected Output\r

A JSON summary of the groomed tasks returned by the plugin.\r

Usage Guidance
This skill is missing critical implementation details. Before installing, ask the publisher these questions: (1) What is 'workflow_backlog_grooming'? Is it a platform-provided plugin or third-party code? (2) Which Google account and OAuth scopes will it use to read/write Google Tasks? Provide the exact auth flow or platform-managed credential mechanism. (3) Where do logs/audit records for grooming operations appear and who can view them? (4) Why is there no homepage, source, or contact info for the owner ID? If you can't get clear answers, test only with a dummy/non-production Google account, or decline installation. Never grant full Google account credentials; prefer scoped OAuth consent and confirm least-privilege access.
Capability Assessment
Purpose & Capability
The skill description says it manages Google Tasks, but the manifest declares no Google credentials, no required env vars, and no binaries. A task-management integration normally needs OAuth credentials/scopes or a documented backend; that required access is not present or explained.
Instruction Scope
Runtime instructions simply tell the agent to execute a native plugin tool named 'workflow_backlog_grooming' with an empty JSON payload and validate the tool's JSON response. The SKILL.md does not document what that plugin is, where it runs, which account it uses, or what data will be read/modified — making the runtime behavior opaque.
Install Mechanism
There is no install specification and no code files; the skill is instruction-only, so nothing is written to disk during install. This is the lower-risk install model.
Credentials
No environment variables, credentials, or config paths are declared despite the skill's stated need to operate on Google Tasks. Either the plugin runs with platform-managed credentials (not disclosed) or the skill omits required auth — both are notable gaps.
Persistence & Privilege
The skill is not marked always:true and uses default invocation settings. It does not request elevated platform persistence or modify other skills' configuration in the provided instructions.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install backlog-grooming
  3. After installation, invoke the skill by name or use /backlog-grooming
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
- Added explicit step-by-step instructions for a Jidoka-validated execution loop during backlog grooming. - Included error checking, retry logic (up to 3 attempts), and user notification on repeated failure. - Clarified the expected input (`{}`) and required JSON response structure from the plugin. - Maintained focus on lean and autonomous principles.
v1.0.1
- Expanded operating system support from "windows" to "all" in the skill metadata.
v1.0.0
- Initial release of the backlog-grooming skill. - Automates management of stale items in Google Tasks, archiving tasks older than 30 days. - Follows lean principles: Kaizen, Standardized Work, and Jidoka. - Provides a JSON summary of groomed tasks upon execution.
Metadata
Slug backlog-grooming
Version 1.0.2
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 3
Frequently Asked Questions

What is Backlog Grooming?

Workflow-driven skill that autonomously manages stale items in Google Tasks. It is an AI Agent Skill for Claude Code / OpenClaw, with 85 downloads so far.

How do I install Backlog Grooming?

Run "/install backlog-grooming" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Backlog Grooming free?

Yes, Backlog Grooming is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Backlog Grooming support?

Backlog Grooming is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Backlog Grooming?

It is built and maintained by zvirb (@zvirb); the current version is v1.0.2.

💬 Comments