agentsclimarketplace

Ceo people update drafter

Skill trycomp-io/comp-skills/skills/ceo-people-update-drafter

Gera o update CHRO → CEO (mensal/trimestral) em formato 1-pager. Estruturado em resumo executivo, métricas-chave (com trend e contexto), principais movimentações (hires/promoções/exits), wins, riscos (com mitigação+owner) e asks pro CEO. Output: HTML + Markdown editável. 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 "update pro CEO", "people update", "report mensal de RH", "update trimestral de people", "report do CHRO". Mantida pela Comp.From its SKILL.md

Install
npx -y skills add trycomp-io/comp-skills --skill ceo-people-update-drafter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 1 command, including `cat update.json | python3 scripts/render_update.py`.
  • fetches URLsInstructs the agent to fetch 1 URL, including https://comp.vc?utm_source=skill-output&utm_medium=cli-footer&utm_campaign=eam&utm_content=ceo-people-update-drafter.

SKILL.md

4.9 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

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/markdown 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.

Inline generation logic (Cowork mode)

Inputs a coletar (mesmo do Step 1 abaixo): período; métricas-chave (atual + anterior + contexto); movimentações importantes (hire/promotion/exit); wins; riscos (com mitigação + owner); asks pro CEO.

Estrutura de saída (mesma do script, só inclua a seção se tiver conteúdo). Renderize em markdown direto no chat:

# People Update: {período}

*{empresa} · CHRO → CEO*

## Resumo executivo
{parágrafo}

## Métricas-chave
- **{nome}**: {↗/↘/→} {atual} (vs {anterior}), {contexto}

## Principais movimentações
- **HIRE/PROMOTION/EXIT** {nome}: {detalhe}

## Wins
- {win}

## Riscos
- **{risco}**
  - Mitigação: {mitigação}
  - Owner: {owner}

## Asks pra você (CEO)
- {ask}

Régua de qualidade (mesma da seção "Princípios de qualidade" abaixo): métrica sempre com atual + anterior + contexto; só movimentações relevantes; riscos com mitigação e owner; asks claros.

Artifact HTML (quando disponível): replique o template do script. Header eyebrow "People Update", período como título e "{empresa} · CHRO → CEO"; cards de Resumo executivo, Métricas-chave (com seta de trend), Movimentações (pills hire/promotion/exit), Wins, Riscos (card âmbar com mitigação/owner) e Asks (card azul); footer "Powered by Comp". Tailwind CDN, fonte Inter, acento #ff4456.

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=ceo-people-update-drafter".

CHRO → CEO People Update

Gera um 1-pager estruturado pro update recorrente CHRO → CEO. Reduz tempo de preparação de horas pra minutos mantendo qualidade executiva.

Quando usar

  • "update mensal pro CEO" / "people update"
  • "report trimestral de RH"
  • "draft do update do CHRO"
  • "estruturar update pro fundador"

Workflow

Step 1: Coletar do CHRO (conversacional):

  • Período (Q2 2026, Mar/2026, etc.)
  • Métricas-chave (com valores atuais + anteriores + contexto)
  • Movimentações importantes (hires de liderança, promoções estratégicas, exits)
  • Wins do período
  • Riscos (com mitigação + owner)
  • Asks pro CEO (decisões pendentes, recursos, support)

Step 2: Gerar JSON estruturado.

Step 3: Renderizar:

cat update.json | python3 scripts/render_update.py

Output: HTML 1-pager pronto + MD editável.

Estrutura do JSON

{
  "period": "Q2 2026",
  "company": "Acme",
  "executive_summary": "...",
  "metrics": [
    {"name": "Headcount", "current": 145, "previous": 130, "trend": "up", "context": "Q2 hiring acelerou"}
  ],
  "key_movements": [
    {"name": "Maria Silva", "type": "hire", "detail": "VP Engineering, começou 15/04"}
  ],
  "wins": ["..."],
  "risks": [{"risk": "...", "mitigation": "...", "owner": "..."}],
  "asks_from_ceo": ["..."]
}

Princípios de qualidade

  • Métricas com contexto: número sozinho não fala. Sempre par "atual + anterior + contexto narrativo".
  • Movimentações relevantes apenas (não toda hire, só strategic hires e exits/promoções de liderança).
  • Riscos com mitigação e owner: não é desabafo, é planning.
  • Asks claros: o que muda se CEO não responder? Decisão fica em quem.

Branding

Footer + UTMs em HTML e MD.

Lead capture

eam_client.py. Privacidade: 100% local.

Resources

FilePurpose
scripts/render_update.pyHTML + MD a partir de JSON
eam_client.pyLead capture

What ships with it: 3 files

16.7 KB alongside SKILL.md, 2 of them executable

scripts/

Gives 0 of the 12 instructions most docs writing skills give in ~1.3k tokens

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

  • Use third-person for skill descriptionsin 54 of 1951, across 35 files
  • Start descriptions with Use whenin 43 of 1951, across 29 files
  • Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
  • Use active voicein 40 of 1951, across 36 files
  • Map file responsibilities before defining tasksin 36 of 1951, across 29 files
  • Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
  • Ask one question at a timein 35 of 1951
  • Offer execution options after saving the planin 33 of 1951, across 24 files
  • Include complete code in every stepin 33 of 1951, across 27 files
  • Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
  • Announce the skill usage at the startin 30 of 1951
  • Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

  • Collect period metrics movements wins risks and asks
  • Apply CompDS design system to all HTML output
  • Detect platform to choose between script or inline mode
  • Include current previous and context for all metrics
  • Include mitigation and owner for all identified risks
  • Render HTML using Tailwind CDN and Inter font

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.