convez.ai
SkillProdutividadeIntermediário
jenn-creator

Claude Executive Assistant Skills

jenn-creator/claude-ea-skills

Template forkável de skills para assistente executivo com Claude Code

Ver no GitHub
InicialPluginScore · de 0 a 100

Biblioteca de skills Python para montar um assistente executivo com Claude Code. Inclui templates prontos para briefings diários, relatórios semanais, pesquisa estruturada e integrações com ClickUp, Gmail, Google Calendar e Stripe. Basta fazer fork, configurar contexto pessoal e customizar as skills.

Instalação

$npx convez-ai jenn-creator/claude-ea-skills

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Gerar briefings diários automáticos com calendário, emails e tarefas
  • Executar pesquisas estruturadas com citações e salvar resultados
  • Automatizar relatórios semanais e wrap-ups com dados de múltiplas fontes
  • Integrar ClickUp, Gmail, Google Drive e Stripe em workflows customizados
  • Criar skills específicas para seu fluxo de trabalho (payroll, reconciliação, agendas)

Veredito

Projeto bem estruturado e prático para quem quer montar um EA real com Claude Code. O framework está sólido, documentação clara, e os exemplos cobrem casos típicos de executivos. Requer setup inicial (contexto + MCP connectors) mas o payoff é alto para quem investe.

README

A tradução para o português deste README ainda está na fila.

Claude Executive Assistant Skills

A forkable template of Claude Code skills for an AI-powered executive assistant. Fork this repo, drop in your own context files, customize the example skills, and have a working EA setup in an afternoon.


What's in the box

Universal skills — work out of the box with your own integrations:

SkillWhat it does
/morningDaily briefing: calendar, DMs, email, tasks
/morning-swarmParallel morning briefing via 4 specialist agents (faster, more thorough)
/weekly-wrapupFriday wrap-up: overdue tasks, deadlines, email follow-ups, next week
/compliance-digestSnapshot of upcoming and overdue compliance obligations
/research-runnerResearch any topic and save structured findings with citations
/cc-statement-analyzerParse credit card statements into a categorized Google Sheet
/grill-meRelentless interview mode — extracts what's in your head into a doc
/lesson-jenn-italianDaily Italian lesson (customize for your own learner)
/lesson-jenn-spanishDaily Spanish lesson
/lesson-d-italianDaily Italian lesson for a second learner
/lesson-d-spanishDaily Spanish lesson for a second learner

Example skills — built for a specific company setup, included as patterns to adapt:

SkillWhat it does
/payroll-hours-chaserDraft and send a ClickUp DM to collect bi-weekly payroll hours
/quickbooks-reconcilerCompare Stripe refunds against QBO entries and produce a handoff doc
/leadership-meeting-agendaBuild and manage the weekly leadership meeting agenda
/friday-ai-updateGenerate and post a weekly AI development summary to a ClickUp channel
/weekly-leadership-reportPull ClickUp tasks, interview on progress, create a Google Doc report

Quick start

1. Fork this repo

Click Fork on GitHub. Clone your fork locally.

2. Fill in your context

Copy the example files in context/ and remove the .example extension:

cp context/me.example.md context/me.md
cp context/work.example.md context/work.md
cp context/team.example.md context/team.md
cp context/current-priorities.example.md context/current-priorities.md
cp context/goals.example.md context/goals.md

Edit each file to describe yourself, your company, your team, and your current priorities. Claude reads these files at the start of every session.

3. Configure settings

cp .claude/settings.example.json .claude/settings.json

Edit .claude/settings.json — update any hook paths to match your local setup. Remove hooks for skills you're not using.

4. Connect your MCP tools

The skills use these MCP connections. Connect the ones you use at claude.ai/customize/connectors:

  • ClickUp — tasks and DMs
  • Gmail — email
  • Google Calendar — calendar events
  • Google Drive — document creation
  • Stripe — payment and refund data

The morning and morning-swarm skills also use the gws CLI for Google Workspace. Install it separately if you use those skills.

5. Run a skill

Open Claude Code in your repo directory and type the skill name:

/morning
/weekly-wrapup
/research-runner

Customizing the example skills

The five example skills are built around a specific company's setup — they contain placeholder values like [YOUR-LIST-ID], [YOUR ACCOUNTANT], and [YOUR PAYROLL CONTACT] that you need to fill in before using them.

How to customize

  1. Open the skill's SKILL.md file
  2. Search for [YOUR — every placeholder follows that pattern
  3. Replace each one with your real value

Common placeholders:

PlaceholderWhat to replace it with
[YOUR NAME]Your name
[YOUR COMPANY]Your company name
[YOUR EMAIL]Your email address
[YOUR ACCOUNTANT]Your accounting firm or contact
[YOUR HR PLATFORM]Your HR/payroll platform (e.g., Gusto, Rippling, Justworks)
[YOUR-LIST-ID]Your ClickUp list ID (find it in the ClickUp URL)
[YOUR-USER-ID]Your ClickUp user ID
[YOUR-CHANNEL-ID]Your ClickUp channel ID
[YOUR-DRIVE-ID]Your Google Shared Drive ID
[YOUR-FOLDER-ID]Your Google Drive folder ID

Adding your own skills

Skills are just markdown files. Create a new folder under .claude/skills/ with a SKILL.md inside:

.claude/skills/my-skill/SKILL.md

The SKILL.md has a short YAML frontmatter block followed by the skill instructions:

---
name: my-skill
description: "One sentence describing what this skill does and when to use it."
---

# My Skill

Instructions for Claude go here. Be specific about steps, tools to use,
and what the output should look like.

Invoke it in Claude Code with /my-skill.

Minimum requirements for new skills

Before committing a new skill:

  • Add .claude/skills/<skill-name>/tests/test_static.py with at least 5 structural checks
  • Add .claude/skills/<skill-name>/tests/fixtures/all_ok.yaml with a passing behavioral fixture
  • If the skill includes write operations (Drive, Sheets, ClickUp, git): include at least one confirmation gate check

See morning-swarm/tests/ for a full example of static + behavioral tests.


Running tests

# Full suite (static + behavioral — behavioral requires Claude CLI)
python .claude/tests/run_all.py

# Static checks only (fast, no Claude calls)
python .claude/tests/run_all.py --static-only

Behavioral tests invoke Claude via the CLI and cost tokens. Run them before committing skill changes.

Snapshot tests auto-create on first run. If you intentionally change a skill's output format, delete the snapshot file and re-run to regenerate it:

rm .claude/skills/morning-swarm/tests/snapshots/all_ok_expected.txt
python .claude/tests/run_all.py

Repo structure

.claude/
  rules/                  # Persistent instructions Claude follows every session
  skills/                 # All skills — one folder per skill
    morning/
      SKILL.md
    morning-swarm/
      SKILL.md
      tests/
        test_static.py
        test_behavioral.py
        fixtures/
        snapshots/
    ...
  settings.example.json   # Copy to settings.json and customize
  tests/
    run_all.py            # Test suite entry point
    lib/
      assertions.py
      fixture_loader.py
      skill_runner.py

context/
  me.example.md           # Copy to me.md — who you are
  work.example.md         # Copy to work.md — your company and tools
  team.example.md         # Copy to team.md — your team
  current-priorities.example.md
  goals.example.md

templates/
  session-summary.md      # Template for closing out working sessions

decisions/                # Important decisions log (append-only)
projects/                 # Active workstreams
archives/                 # Old files moved here instead of deleted

Context files

Claude reads your context files at the start of every session. Keep them current:

  • When focus shifts → update context/current-priorities.md
  • Start of each quarter → update context/goals.md
  • After important decisions → log in decisions/log.md
  • When a workflow keeps repeating → build a skill

Requirements

  • Claude Code (CLI or desktop app)
  • Python 3.11+ (for tests)
  • pytest and pyyaml (pip install pytest pyyaml)
  • MCP connectors for the tools your skills use
  • gws CLI for morning and morning-swarm skills (Google Workspace)
Ver o original no GitHub

Bom para

Relacionados