agentleFS
rubixkube-iorubixkube-io/rubixkube-for-ai/skills/tasks/SKILL.md

tasks

Skill1 starsChanged 36 days agoMITView on GitHub

Tasks are the Fixes and Follow-ups an RCA proposes or a person adds. List them, read one, create one, rename or reprioritise, move between statuses, assign. Use when the person asks what to work on, about action items or fixes, or wants to create, assign or close a Task.

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use send-user-message, tinyagi-admin and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Maliot100XSkill

    send-user-message

    Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp). Use when the agent needs to notify, alert, or send an unsolicited message to a user — especially during heartbeat invocations, scheduled tasks, or when the agent wants to reach out without a prior user message in the current conversation. Triggers: 'send message to user', 'notify user', 'alert user', 'message the user on discord/telegram/whatsapp', or any need to proactively communicate with a paired sender.

    Also in 4 projects that use this

  • jlia0Skill

    tinyagi-admin

    Manage and operate the TinyAGI system itself — agents, teams, settings, queue, tasks, daemon lifecycle, and source code. Use when the agent needs to: list/add/remove/update agents or teams, check queue status, view logs, start/stop/restart TinyAGI, change settings (provider, model, channels), send messages to the queue, manage tasks, retry dead-letter messages, view recent responses, modify TinyAGI source code or configuration, or perform any administrative operation on the TinyAGI platform. Triggers: 'manage tinyagi', 'add an agent', 'remove a team', 'check queue', 'view logs', 'restart tinyagi', 'change provider', 'update settings', 'create a task', 'modify tinyagi code'.

    Also in 3 projects that use this

  • ArvorCoSkill

    constitution

    Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.

    Also in 4 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 6 projects that use this

  • GoogleSkill

    quality

    Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

    Also in 3 projects that use this

  • anyprotoSkill

    skills-manager

    Context-aware routing to skills and hooks management. Use when troubleshooting skill activation, fine-tuning keywords, or managing the automated documentation system.

    Also in 3 projects that use this

  • +1 more from ArvorCo

The file

Files
SKILL.md

When to use

  • "What should I work on?" / "Show me the open Tasks" / "What's assigned to me?"
  • "Create a Task to raise the memory limit" / "Assign it to Sam" / "Mark it done"
  • "Turn this RCA into Tasks"

Tools

  • list_tasks(status="todo,in_progress", priority?, limit?): statuses todo, assigned, in_progress, waiting, review, completed, failed, cancelled; priority critical, high, medium, low. Each row has kind (fix or follow_up), assignee, links to incident and RCA, and the console link.
  • get_task(task_id) for the description, links and history.
  • create_task(environment_id, title, priority, kind, description?, incident_id?, rca_id?, owner_email?). Link it to the incident and RCA it came from.
  • update_task(task_id, title?, priority?).
  • move_task(task_id, to, comment): the comment says why. Allowed moves are in the tool description; a wrong move is refused with the reason.
  • assign_task(task_id, owner_email?): a member's email, or empty to unassign.
  • list_comments(kind="task", id) and post_comment(kind="task", …).

How to answer

Group by priority, then by status. Say who owns each Task. Before creating, moving or assigning, show what you are about to do and wait for a yes: these are recorded under the person's name. When turning an RCA into Tasks, check list_tasks first so you do not file duplicates. The server offers this as the turn_rca_into_tasks prompt.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.