openclaw-yatta-skill_skill

This skill helps you manage tasks and capacity across projects with AI insights, Eisenhower prioritization, and real-time scheduling.
  • Python

1.7k

GitHub Stars

5

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill openclaw-yatta-skill

  • _meta.json315 B
  • API-REFERENCE.md22.1 KB
  • package.json961 B
  • README.md7.2 KB
  • SKILL.md19.0 KB

Overview

This skill connects to the Yatta! personal productivity system to manage tasks, projects, contexts, calendar subscriptions, follow-ups, and capacity planning. It exposes read and write operations via the API so you can create, update, archive, batch-modify items, trigger capacity computations, and fetch AI-driven insights. Use an API key to authenticate; keys grant full account access so handle them with care.

How this skill works

The skill issues HTTP requests against the Yatta! API endpoints to list and filter tasks, projects, contexts, comments, calendar subscriptions, follow-ups, capacity and analytics. Read-only operations use GET; destructive actions (create/update/delete/batch) use POST, PUT, or DELETE and apply changes immediately in the Yatta! account. It supports pagination, matrix-state filters, recurrence and follow-up scheduling, and triggering server-side capacity computation.

When to use it

  • Automate creating, updating, or archiving tasks across projects
  • Fetch prioritized work using Eisenhower Matrix filters or priority/effort tags
  • Sync external calendars and create calendar-based tasks or contexts
  • Run capacity checks before committing to new work or to detect overcommitment
  • Batch-update many tasks or reassign work and follow-up schedules

Best practices

  • Store the Yatta! API key in a secure secret store or environment variable; never hardcode keys
  • Test destructive operations on non-critical or test data before running against production
  • Review API calls and affected IDs before running batch updates or deletes
  • Rotate and revoke API keys regularly and create separate keys per integration
  • Trigger capacity recomputation after major schedule or task changes to keep planning accurate

Example use cases

  • Create a recurring team standup task with effort points and daily recurrence rules
  • Delegate a project task to a team, set a weekly follow-up schedule, and mark follow-ups complete via API
  • List high-priority, overdue tasks across projects to build a focused daily plan
  • Add a calendar subscription for work events and map those events to a default context for time blocking
  • Batch-update a set of tasks to move them into a new project and increase their priority before a release

FAQ

API keys provide full access to your Yatta! account; there are no read-only scopes. Treat keys as highly sensitive credentials.

Can I undo deletes or archives performed via the API?

Archived tasks can typically be recovered, but some destructive operations are permanent. Always test on non-critical data and confirm affected IDs before running destructive calls.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational