og-board-individual

What This Skill Does

The og-board-individual skill serves as a dedicated interface for managing individual task workflows within the OpenClaw agent ecosystem. It allows agents to interact directly with task management systems, enabling seamless viewing, status updates, and logging. Rather than relying on shell CLI commands, this skill provides a structured API-driven approach to task tracking, ensuring consistent state management across project boards. It empowers agents to handle the full lifecycle of their assigned tickets, from initial status changes to providing evidence of completion through artifacts and documenting progress via worklogs.

Installation

You can integrate this skill into your agent workspace by executing the following command in your terminal or via your agent management hub:

clawhub install openclaw/skills/skills/jatin-31/og-board-individual

Ensure that your agent has the necessary permissions to access your organizational project board before invoking the tools. Once installed, initialize your agent context using the opengoat_agent_info tool to verify the connection between your agentId and the task management system.

Use Cases

This skill is essential for agents tasked with autonomous project execution. Common use cases include:

• Automating status transitions: Agents can move tasks to 'done' immediately after completing a codebase update.
• Dependency Tracking: When an agent hits an external bottleneck, it can flag the task as 'blocked' and attach the specific reason, alerting human supervisors.
• Progress Reporting: Using the worklog tool, an agent can leave daily notes for human teammates, providing visibility into complex, multi-day tasks.
• Artifact Archiving: Attaching PR links or documentation updates directly to tasks ensures that all project outputs are centralized and auditable.

Example Prompts

1. "List all my currently assigned tasks for the amazon-catalog-manager agent and identify any that are currently blocked."
2. "Update my task T-102 to 'done' and include a worklog note saying the refactoring is finished and tests have passed."
3. "Mark task T-55 as blocked because I am still waiting for the database credentials from the infrastructure team."

Tips & Limitations

To maximize the efficiency of this skill, ensure that your actorId is always correctly configured to match your agent identity. Remember that while reason codes are optional for some status changes, they are mandatory for 'blocked' or 'pending' statuses; failure to provide them will result in an error. Avoid using this skill to attempt direct shell modifications or file system changes, as it is strictly limited to task management metadata. Keep worklog content concise and informative to ensure the task history remains readable for human project managers.