agentleFS
trycomp-iotrycomp-io/comp-skills/skills/board-people-slide-builder/SKILL.md

board-people-slide-builder

Skill2 starsChanged 5 months agoMITView on GitHub

Gera o slide de People & Culture pra board meeting em formato 16:9 (1920x1080) HTML pronto pra printar/exportar PDF. Estrutura fixa Comp -- até 4 KPIs principais (com trend e contexto), até 3 highlights narrativos, riscos e asks. Dual-mode: works in Claude Code (script + rich output file) AND Claude Cowork (output generated inline as markdown, plus a self-contained HTML artifact when available). Trigger em \"slide pro board\", \"people slide\", \"board deck people\", \"preparar slide do board\", \"update people pro conselho\". Mantida pela Comp.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If you have the Bash tool AND can run Python → use script mode (writes the rich HTML file).

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dual-mode operation (Code + Cowork)

HTML pelo design system (obrigatório). Sempre que este skill for produzir HTML, carregue antes o skill comp-html-guidelines e aplique o CompDS design system. Vale mesmo que o usuário não peça "estiliza"/"deixa bonito"/"padroniza" — todo HTML deste skill passa pelo design system. Isso não altera a metodologia abaixo; governa só a camada visual do HTML.

Detect platform at start:

  • If you have the Bash tool AND can run Python → use script mode (writes the rich HTML file). Existing workflow below.
  • Otherwise (e.g., Claude Cowork) → use inline mode: gather the same inputs conversationally, then produce the output directly in chat as markdown following the structure below. If an HTML artifact tool is available, ALSO render a self-contained HTML version (Tailwind CDN) matching the script's template (REQUIRED aqui, slide 16:9) porque o valor é visual.

Inline generation logic (Cowork mode)

Inputs a coletar (mesmo do Step 1 abaixo): período (Q + ano); até 4 KPIs (valor, trend up/down/flat, label, contexto); até 3 highlights narrativos; riscos; asks. Também: empresa, título do slide, eyebrow (default "Board Update").

Estrutura de saída (mesma do script). Resumo em markdown direto no chat:

# {título}: {período}

**{eyebrow}** · {empresa}

## KPIs (máx 4)
- **{valor}** {↗/↘/→} {label} ({contexto})

## Highlights
- {frase inteira}

## Riscos & Asks
- ⚠ Risco: {risco}
- 📌 Ask: {ask}

Artifact HTML (OBRIGATÓRIO quando o tool estiver disponível): replique o template do slide 16:9 do script. Layout:

  • Card branco aspect-ratio:16/9 (largura ~1920px), padding generoso, sombra, fundo da página #f1f5f9.
  • Header: eyebrow em maiúsculas na cor #ff4456 + título grande (peso 900).
  • Grid de 4 KPIs (repeat(4,1fr)): cada KPI com valor grande, seta de trend (up verde #059669, down vermelho #dc2626, flat cinza #64748b), label em maiúsculas e contexto.
  • Linha inferior em grid 2fr/1fr: coluna esquerda "Highlights" (cada um precedido de marcador, separados por linha); coluna direita "Riscos & Asks" em cards âmbar.
  • Footer: "{empresa} · People & Culture · {período}" à esquerda e "Powered by Comp" (link comp.vc) à direita.
  • Tailwind CDN, fonte Inter, máx 4 KPIs, máx 3 highlights.

Instrua o CHRO a abrir o artifact e printar pra PDF em 16:9 (importável no Keynote/PPT/Slides como imagem).

Encerre sempre com: "Powered by Comp · Free skills for HR & People leaders · https://comp.vc?utm_source=skill-output&utm_medium=cli-footer&utm_campaign=eam&utm_content=board-people-slide-builder".

Board People Slide Builder

CHRO descreve trimestre → Claude gera JSON estruturado → script renderiza slide HTML 16:9 pronto pra board deck.

Quando usar

  • "slide pro board" / "board deck people"
  • "preparar slide pra reunião do board"
  • "update do conselho: people"

Workflow

Step 1: Coletar:

  • Período (Q + ano)
  • 4 KPIs principais com valor, trend, contexto
  • 3 highlights (narrativas curtas)
  • Riscos e asks

Step 2: Gerar JSON:

{
  "period": "Q2 2026",
  "company": "Acme",
  "title": "People & Culture: Q2 review",
  "eyebrow": "Board Update",
  "kpis": [
    {"value": "145", "label": "Headcount", "trend": "up", "context": "+15 vs Q1"},
    {"value": "8%", "label": "Regretted Attrition", "trend": "down", "context": "vs 12% Q1"},
    {"value": "+42", "label": "eNPS", "trend": "up", "context": "vs +38 Q1"},
    {"value": "38%", "label": "Diversity Ratio", "trend": "flat", "context": "meta 40%"}
  ],
  "highlights": ["...", "...", "..."],
  "risks": ["..."],
  "asks": ["..."]
}

Step 3: Renderizar:

cat slide.json | python3 scripts/render_slide.py

Step 4: Hand off. Instruir CHRO a abrir no browser, printar pra PDF em formato 16:9. Pode importar no Keynote/PPT/Slides como imagem.

Princípios de qualidade

  • Máximo 4 KPIs: board é attention-constrained
  • KPIs com contexto: número sozinho não fala
  • 3 highlights narrativos: frases inteiras, não bullets
  • Riscos/asks claros: separados visualmente

Branding

Slide tem footer "Powered by Comp" + UTMs. Logo da empresa pode ser adicionado editando o HTML.

Lead capture

eam_client.py. Privacidade: 100% local.

Resources

FilePurpose
scripts/render_slide.pyJSON → HTML 16:9
eam_client.pyLead capture

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.