reuniao-de-resultado

reuniao-de-resultado is a skill for Claude Code, Codex from tatagoncalvesof/imperatriz-toolkit. It costs 237 tokens per session (3,016 once invoked), scanned A, original, MIT.

A business-meeting system that helps an owner design, run, and improve regular performance-review meetings. It produces an interactive HTML dashboard and files for an Obsidian Vault, a folder of linked notes.

In plain words
What is it for?
Use it to diagnose meeting problems, choose useful indicators, prepare an agenda, record meeting notes, find root causes, and create an action plan.
Why use it?
It helps replace meetings that end without decisions with a repeatable process for reviewing results and agreeing on actions. It can also assess an existing meeting or build one from the beginning.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to diagnose meeting problems, choose useful indicators, prepare an agenda, record meeting notes, find root causes, and create an action plan.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tatagoncalvesof/imperatriz-toolkit/reuniao-de-resultado
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add tatagoncalvesof/imperatriz-toolkit --skill reuniao-de-resultado
Clone the repo
git clone --depth 1 https://github.com/tatagoncalvesof/imperatriz-toolkit

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for reuniao-de-resultado

README.md
[![agentmods](https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/reuniao-de-resultado/github.svg)](https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/reuniao-de-resultado)
Your own site
<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/reuniao-de-resultado"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/reuniao-de-resultado/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for reuniao-de-resultado

Your own site · 80×15
<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/reuniao-de-resultado"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/reuniao-de-resultado.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 237 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,016 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00237 $0.03016
Opus 5 $0.00118 $0.01508
Sonnet 5 $0.00047 $0.00603
Haiku 4.5 $0.00024 $0.00302

Measured 12d ago against content hash 9607ec7644db, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

reuniao-de-resultado scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/reuniao-de-resultado/SKILL.md · 156 lines

How it starts

The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Reunião de Resultado — Skill Imperatriz

Skill proprietária da Tata Gonçalves. Constrói o sistema completo de Reunião de Resultado pra qualquer negócio — diagnóstico, estrutura, condução, implementação e primeira reunião — em pacote pronto pra usar (HTML + arquivos no vault).

Overview

Reunião de Resultado é o ritual gerencial que transforma reunião que não decide nada em reunião que faz dinheiro. O método tem 6 blocos sequenciais (diagnóstico → estrutura → core → condução → implementação → primeira reunião) e essa skill empacota TUDO em entregáveis prontos pra uma empresária implementar na semana que vem.

Dois modos de uso — escolha um no início da conversa:

  • Modo Transcrição — a usuária cola transcrição de uma reunião que já faz hoje. A skill diagnostica os 7 sintomas, mapeia os erros do bloco 5, e entrega plano de transformação personalizado.
  • Modo Do Zero — a usuária ainda não tem reunião estruturada. A skill faz entrevista curta (5 perguntas) e monta o sistema completo do zero.

Em ambos os modos, o output final é o mesmo: HTML standalone + 14 arquivos no Obsidian Vault.

Workflow Decision Tree

1. Detectar modo (perguntar se ainda não está claro)
   ├── Modo A: TRANSCRIÇÃO
   │   ├── Aceitar transcrição
   │   ├── (opcional) sugerir /transcript-fixer se vier crua de STT
   │   ├── Diagnosticar 7 sintomas (references/bloco-1-diagnostico.md)
   │   ├── Mapear contra 7 erros (references/bloco-5-implementacao.md)
   │   ├── Resumir gaps em 1 página
   │   └── Seguir pra construção do pacote
   │
   └── Modo B: DO ZERO
       ├── 5 perguntas de briefing (ver "Briefing Mínimo" abaixo)
       ├── (opcional) sugerir /mecanismo-unico se a usuária não souber
       │   o que diferencia o negócio dela — ajuda a escolher os 2-3
       │   indicadores que importam
       └── Seguir pra construção do pacote

2. Construir pacote (sempre igual nos dois modos)
   ├── Ler os 6 references/ pra absorver método
   ├── Personalizar templates de assets/vault-templates/ com dados do briefing/diagnóstico
   ├── Personalizar assets/dashboard-template.html
   ├── Passar comunicado pro grupo + roteiro 1ª reunião por /voz-humana-br
   │   (obrigatório — não entregar texto sem humanizar)
   └── Salvar tudo no destino

3. Entregar
   ├── Vault: ~/Documents/Obsidian Vault/03 - Projetos/Reuniao-Resultado-{NEGOCIO}/
   ├── HTML: mesma pasta, arquivo dashboard.html
   └── Resumo final no chat: lista dos 15 arquivos + próxima ação

4. Modo pós-construção (se a usuária voltar depois)
   ├── "Auditar minha reunião de ontem" → roda diagnóstico em transcrição nova
   ├── "Refazer ata" → atualiza só o template de ata
   ├── "Plano de ação pra meta X em risco" → gera só o plano (bloco 3)
   └── "Roteiro pra próxima reunião" → gera só o roteiro

Read the full file on GitHub · 156 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 156 lines · 237 tokens per session scan A 9607ec7644db

Subscribe to this mod's changes

reuniao-de-resultado is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 237 tokens to every session and 3,016 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

create-request

Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…

sd0xdev/sd0x-harness · 112 tokens

req-analyze

A requirements-analysis tool that breaks a problem into needs, stakeholders, and priorities before a technical solution is chosen.

sd0xdev/sd0x-harness · 101 tokens

recap-ask

Interactive Q&A over an existing recap document. Use when: user wants to ask follow-up questions about a briefing-recap- .md produced by /recap-doc, with recap-bounded context + out-of-scope redirect + optional promote-to-request. Not for: generating a new recap (use /recap-doc), general project Q&A (use /ask), code…

sd0xdev/sd0x-harness · 106 tokens

recap-doc

Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…

sd0xdev/sd0x-harness · 114 tokens

runbook

Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).

sd0xdev/sd0x-harness · 59 tokens

jira

Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).

sd0xdev/sd0x-harness · 64 tokens