Agent skill

prod-review-todoist

Review and organize Todoist tasks in the Evolution project. Finds uncategorized, untranslated, or messy tasks and organizes them with proper categories, PT-BR translation, and actionable titles. Use when user says 'review todoist', 'organize tasks', 'todoist triage', 'clean up todoist', or similar.

Stars 211
Forks 54

Install this agent skill to your Project

npx add-skill https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/prod-review-todoist

SKILL.md

Review Todoist — Evolution Project Triage

Skill to review and organize tasks in the Evolution Todoist project. Identifies uncategorized, English-only, generic, or disorganized tasks and fixes them directly.

Prerequisites

  • CLI todoist installed and authenticated
  • Evolution project existing in Todoist

Workflow

Step 1 — List Evolution project tasks

bash
todoist tasks -p "Evolution"

Step 2 — Identify tasks that need organization

A task needs triage if it meets any of these criteria:

  1. No category — does not have [Categoria] prefix in the title
  2. In English — title is not in PT-BR
  3. Generic/vague — title does not make clear what to do (ex: "update thing", "send docs")
  4. No context — no comment with origin/objective (especially tasks from sync-meetings)

Step 3 — Organize each task

For each task that needs triage, apply:

3a. Categorize

Add [Categoria] prefix to the title. Available categories:

Category When to use
[Produto & Tech] Development, bugs, features, infra, deploy, code
[Marketing] Content, campaigns, videos, social media, launches
[Sales] Pipeline, proposals, partnerships, leads, pricing
[Financial] Accounts, invoices, payments, financial metrics
[Operations] Internal processes, groups, access, team communication
[Strategy] OKRs, roadmap, analyses, strategic decisions
[Community] Discord, support, user feedback, beta testers
[Roadmap] Future roadmap items, feature evaluation

3b. Translate to PT-BR

If the title is in English, translate to Brazilian Portuguese keeping clarity and objectivity.

Before: Send event registration link to team member After: [Operação] Enviar link de inscrição do evento para membro do time

3c. Make actionable

The title should make clear:

  • What to do (infinitive verb)
  • For whom/where (if applicable)
  • Expected result (if not obvious)

Before: Upload web panel; grant team member access After: [Operação] Publicar painel web do evento e liberar acesso para membro do time

3d. Apply the update

bash
todoist update <task-id> --content "[Categoria] Título traduzido e acionável"

Step 4 — Execute directly

Fundamental rule: execute the organization directly, without an intermediate report.

Do not list tasks before organizing. Do not ask for confirmation on each one. Organize all at once and confirm at the end.

Step 5 — Save artifact

Save a short report to workspace/daily-logs/[C] YYYY-MM-DD-todoist-review.md com:

markdown
# Todoist Triage — YYYY-MM-DD

**Project:** Evolution
**Tasks reviewed:** {N}
**Organized:** {M} (categorized, translated, or rewritten)
**Already OK:** {K} (no changes needed)

## Organized Tasks

| Task | Before | After |
|--------|-------|--------|
| ... | ... | ... |

Create the directory workspace/daily-logs/ if it does not exist.

Step 6 — Final report (short)

When finished, present only:

## Todoist Triage — Completed

**Project:** Evolution
**Tasks reviewed:** {N}
**Organized:** {M} (categorized, translated, or rewritten)
**Already OK:** {K} (no changes needed)

If the user wants to see details of what changed, they ask.

Important Rules

  • Default project is always Evolution — do not move tasks to other projects
  • Always translate to PT-BR — no exceptions
  • Do not modify already organized tasks (that already have [Category] and are in PT-BR)
  • Do not complete or delete tasks — only reorganize
  • Do not create new tasks — only edit existing ones
  • Keep existing comments — do not modify comments, only the title
  • If unsure about the category, use [Operations] as fallback
  • Execute first, report after — no intermediate report

Notify via Telegram

Upon completion, send a short summary via Telegram to the user:

  • Use the Telegram MCP: reply(chat_id="YOUR_CHAT_ID", text="...")
  • Format: emoji + routine name + main result (1-3 lines)
  • If the routine had no updates, send anyway with "no updates"

Expand your agent's capabilities with these related and highly-rated skills.

EvolutionAPI/evo-nexus

data-create-viz

Cria visualizações de dados de qualidade profissional com Python no tema Evolution (fundo escuro, acento

211 54
Explore
EvolutionAPI/evo-nexus

cs-customer-escalation

Empacota uma escalação para Devs, Produto ou Davidson com contexto completo. Use quando um bug precisa de atenção além do suporte normal, vários clientes reportam o mesmo problema, um cliente está ameaçando cancelar, ou um problema ficou sem resolução além do SLA. / Package an escalation for engineering, product, or leadership with full context. Use when a bug needs engineering attention beyond normal support, multiple customers report the same issue, a customer is threatening to churn, or an issue has sat unresolved past its SLA.

211 54
Explore
EvolutionAPI/evo-nexus

mkt-draft-content

Draft blog posts, social media, email newsletters, landing pages, press releases, and case studies with channel-specific formatting and SEO recommendations. Use when writing any marketing content, when you need headline or subject line options, or when adapting a message for a specific platform, audience, and brand voice.

211 54
Explore
EvolutionAPI/evo-nexus

gog-tasks

Create, manage, and prioritize tasks and todo items. Convert emails to tasks, set priorities (P0-P3) and categories (Work/Personal/Errands/Admin), review daily priorities, track blocked and overdue tasks. Use when user mentions tasks, todos, action items, or wants to convert emails to tasks. Requires confirmation before creating or deleting tasks.

211 54
Explore
EvolutionAPI/evo-nexus

discord-get-messages

Retrieve messages from Discord channels via the Discord API. Use this skill when the user wants to read, search, or analyze messages from a Discord channel.

211 54
Explore
EvolutionAPI/evo-nexus

cs-customer-research

Pesquisa multi-fonte sobre pergunta ou tópico de cliente com atribuição de fontes. Use quando um cliente pergunta algo que precisa ser verificado, investigando se um bug foi reportado antes, verificando o que foi dito anteriormente a uma conta específica, ou coletando contexto antes de redigir uma resposta. / Multi-source research on a customer question or topic with source attribution. Use when a customer asks something you need to look up, investigating whether a bug has been reported before, checking what was previously told to a specific account, or gathering background before drafting a response.

211 54
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results