Connect Apps with Composio
ComposioHQ/awesome-claude-skills
Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.
Generate a daily briefing dashboard that pulls calendar, email, and news into one interactive HTML page.
Install Morning Briefing
$ npx skills add TheCraigHewitt/skills --skill morning-briefing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheCraigHewitt/skills morning-briefing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cowork/morning-briefing .claude/skills/morning-briefing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "morning-briefing" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/morning-briefing into .claude/skills/morning-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "morning-briefing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/TheCraigHewitt/skills/tree/main/cowork/morning-briefingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add TheCraigHewitt/skills --skill morning-briefing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheCraigHewitt/skills morning-briefing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cowork/morning-briefing .agents/skills/morning-briefing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "morning-briefing" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/morning-briefing into .agents/skills/morning-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "morning-briefing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill morning-briefing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheCraigHewitt/skills morning-briefing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cowork/morning-briefing .cursor/skills/morning-briefing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "morning-briefing" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/morning-briefing into .cursor/skills/morning-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "morning-briefing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/TheCraigHewitt/skills.git --path cowork/morning-briefing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add TheCraigHewitt/skills --skill morning-briefing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheCraigHewitt/skills morning-briefing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cowork/morning-briefing .gemini/skills/morning-briefing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "morning-briefing" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/morning-briefing into .gemini/skills/morning-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "morning-briefing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install TheCraigHewitt/skills morning-briefingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add TheCraigHewitt/skills --skill morning-briefing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/cowork/morning-briefing .github/skills/morning-briefing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "morning-briefing" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/morning-briefing into .github/skills/morning-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "morning-briefing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill morning-briefing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TheCraigHewitt/skills morning-briefing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cowork/morning-briefing .opencode/skills/morning-briefing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "morning-briefing" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/morning-briefing into .opencode/skills/morning-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "morning-briefing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
morning-briefing- GitHub stars
- 159
- Token cost
- ~1.3k tokens
- SKILL.md length
- 694 words
- Files
- 2
- Skills in repo
- 65
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generate a daily briefing dashboard that pulls calendar, email, and news into one interactive HTML page.
- Works in 2 steps: briefing-YYYY-MM-DD.html — an… → A short Slack-ready summary — printed in…
- Says morning briefing
- SKILL.md covers What you produce, Before you start, Gather the data and Dashboard structure, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Morning Briefing is an agent skill from TheCraigHewitt/skills. Generate a daily briefing dashboard that pulls calendar, email, and news into one interactive HTML page. Use this whenever the user says 'morning briefing,' 'daily briefing,' 'what's on today,' 'start my day,' 'good morning,' 'daily report,' 'today's agenda,' or asks for a summary of their day, schedule, or inbox first thing in the morning. Also use when the user wants to set up a recurring daily report or scheduled task that runs each morning. Trigger even when the user doesn't explicitly say 'briefing' — any…
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/evals.json`).
It sits in Productivity & Automation, covering Email management, HTML artifacts and Scheduled and recurring tasks. It works with Slack. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.
When your agent uses it
- Says morning briefing
- Asks for a summary of their day
- Inbox first thing in the morning
- The user wants to set up a recurring daily report
Example prompts
- “morning briefing,”
- “daily briefing,”
- “s on today,”
- “/morning-briefing”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- briefing-YYYY-MM-DD.html — an interactive dashboard saved to the current working folder
- A short Slack-ready summary — printed in chat so it can be copied or sent via a Slack connector
What it can do on your machine
Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Morning Briefing loads about 1.3k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 694 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 694 words, ~1,339 tokens.
Download SKILL.mdSave it as
.claude/skills/morning-briefing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- morning-briefing
- description
- Generate a daily briefing dashboard that pulls calendar, email, and news into one interactive HTML page. Use this whenever the user says 'morning briefing,' 'daily briefing,' 'what's on today,' 'start my day,' 'good morning,' 'daily report,' 'today's agenda,' or asks for a summary of their day, schedule, or inbox first thing in the morning. Also use when the user wants to set up a recurring daily report or scheduled task that runs each morning. Trigger even when the user doesn't explicitly say 'briefing' — any 'what should I focus on today' question qualifies.
Morning Briefing
You generate the user's daily briefing: one interactive HTML dashboard plus a short Slack-ready summary. The point is to replace 30 minutes of inbox-skimming, calendar-checking, and news-scanning with a 2-minute scan of a single page.
What you produce
Two artifacts:
briefing-YYYY-MM-DD.html— an interactive dashboard saved to the current working folder- A short Slack-ready summary — printed in chat so it can be copied or sent via a Slack connector
Before you start
Check for a BUSINESS_CONTEXT.md or briefing-config.md in the working folder. If it exists, read it — it should tell you which connectors to use, what news sources matter, what counts as urgent, and which sections to include or skip.
If neither exists, ask the user once:
- Which connectors do you have? (Gmail, Google Calendar, Slack, Notion, etc.)
- Any news topics you want tracked? (AI, fintech, your industry, specific companies)
- What counts as urgent in your inbox? (clients, investors, specific senders)
Save the answers as briefing-config.md for future runs. Don't ask again on subsequent days.
Gather the data
Pull the following, in parallel where possible:
- Today's calendar — all events, with attendees, location/link, and meeting type
- Unread + flagged email — count, top 5 most important by recency + sender importance
- Pending Slack DMs and @mentions — count + top 3
- News headlines — 3–5 items relevant to the user's tracked topics, from the last 24 hours
- Yesterday's loose ends — any sent emails awaiting reply, any tasks marked for today
If a connector isn't available, skip that section rather than guessing. Note the gap at the bottom of the dashboard.
Dashboard structure
Build a single-file HTML page, mobile-friendly, with these sections in order:
- Hero strip — today's date, weather (if connector available), a one-sentence "shape of the day" written by you ("4 meetings, 2 deep-work blocks, one decision needed")
- Schedule timeline — visual timeline of today's meetings, color-coded by meeting type. Click an event for prep notes if available.
- Inbox snapshot — unread count, top 5 emails with sender, subject, one-line summary, and a suggested action (reply / archive / flag / defer)
- Slack pulse — open DMs and @mentions worth responding to
- News — 3–5 cards with headline, source, one-sentence "why it matters to you"
- Loose ends — sent emails over 48 hours old without a reply, prior-day tasks not yet done
- Today's one thing — your read on the single most important thing the user should do today, given everything above
Style: clean, dense, scannable. Light theme by default. Use a small accent color for callouts. No animations beyond hover states.
Show full SKILL.md (278 more words)Show less
Slack summary format
Plain text, under 600 characters, structured like:
☀️ Morning briefing — [Date]
📅 [N] meetings today. First: [time + name]. Watch: [the one to be sharp for]
📥 [N] unread, [N] flagged. Urgent: [sender / topic]
💬 [N] Slack DMs waiting
📰 Notable: [one headline + one-line why it matters]
🎯 Today's one thing: [your call]
Full dashboard: [filename]Why this matters
The user opens this once at the start of the day and decides what to do. If the dashboard is cluttered, generic, or full of stuff they already knew, it has failed — they'll go back to manually checking everything. Optimize for the moment they scan it: every section should either tell them something they didn't already know, or surface something they were about to forget.
Running on a schedule
After the user runs this manually once and likes the output, suggest scheduling it:
"Want me to run this every weekday morning at 7am? I can turn this into a scheduled task that delivers the dashboard and pings you on Slack."
If yes, set up a recurring scheduled task with the appropriate cron schedule. The scheduled version should write the dashboard to a briefings/ subfolder, named by date, so the user builds up a history they can search later.
Rules
- Specificity beats completeness. Three sharp insights > a comprehensive but generic dump. If you're padding to fill a section, cut the section.
- Don't summarize what they wrote. If the user's own sent email is in the inbox, don't summarize it back at them.
- Your read matters. The "Today's one thing" line is the only place you get to play strategist. Use it. Make a real call.
- Be useful when connectors fail. If Gmail is down, still produce the dashboard with the sections you can fill. Note what's missing at the bottom, not at the top.
- Don't include sensitive content in the Slack summary. Subjects and senders are fine; body content is not.
© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in cowork/morning-briefing of TheCraigHewitt/skills.
- SKILL.md
- evals/evals.json
Open the folder on GitHubat commit fdbf39b
Compare with similar skills
Morning Briefing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Morning Briefing this skillTheCraigHewitt/skills | 159 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Connect Apps with ComposioComposioHQ/awesome-claude-skills | 77k | 3 repos | ~557 | Automated safety check: Pass | None | |
| Superset Automatesuperset-sh/superset | 15k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Composio Cloud Toolsquarqlabs/argus | 279 | — | ~543 | Automated safety check: Pass | Apache-2.0 | |
| Executive Digestmgonto/executive-assistant-skills | 118 | — | ~2.6k | Automated safety check: Notes | None | |
| Inbox Archiveyc-software/recruiting | 115 | — | ~1.2k | Automated safety check: Notes | None |
Similar skills
Superset Automate
superset-sh/superset
Turns a recurring chore into a scheduled or event-triggered Superset agent, drafting its prompt, picking a target and trigger, and reviewing the first run.
Composio Cloud Tools
quarqlabs/argus
Routes requests to external SaaS apps such as GitHub, Gmail, Google Calendar, Slack, Notion and Linear through cloud tools, with safeguards on irreversible actions.
Executive Digest
mgonto/executive-assistant-skills
Generate the daily executive digest — a single WhatsApp summary of everything needing attention: stalled scheduling, pending intros, unanswered emails, promised follow-ups, open Todoist tasks, and…
Inbox Archive
yc-software/recruiting
Suggest inbox emails that are "complete" and safe to archive.
Company Brain Follow Up Agent
topoteretes/cognee
Turn your latest Granola call into next steps (owner, team, due date, and the Linear issue that already tracks each one) and post them to Slack, using cognee memory of your calls, Linear issues and…
More from TheCraigHewitt/skills
All 65 skills in this repoCarousels
TheCraigHewitt/skills
Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.
Audience Research
TheCraigHewitt/skills
When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.
Brain Dump
TheCraigHewitt/skills
Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.
Channel Audit
TheCraigHewitt/skills
When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.
Channel Strategy
TheCraigHewitt/skills
When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.
Cold Call
TheCraigHewitt/skills
When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.
Related
Works with
Categories
Questions about Morning Briefing
What does Morning Briefing do?
Generate a daily briefing dashboard that pulls calendar, email, and news into one interactive HTML page. Morning Briefing is an agent skill from TheCraigHewitt/skills. Generate a daily briefing dashboard that pulls calendar, email, and news into one interactive HTML page.
When should I use Morning Briefing?
Morning Briefing fits situations like: says morning briefing; asks for a summary of their day; inbox first thing in the morning; the user wants to set up a recurring daily report.
How do I install Morning Briefing in Claude Code?
Run `npx skills add TheCraigHewitt/skills --skill morning-briefing -a claude-code`. Or copy the skill folder (cowork/morning-briefing in TheCraigHewitt/skills) into .claude/skills/morning-briefing in your project. Claude Code loads it when a task matches its description.
How do I install Morning Briefing in Codex?
Run `npx skills add TheCraigHewitt/skills --skill morning-briefing -a codex`. Or copy the skill folder (cowork/morning-briefing in TheCraigHewitt/skills) into .agents/skills/morning-briefing in your project. Codex loads it when a task matches its description.
Can I use Morning Briefing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill morning-briefing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/morning-briefing, .gemini/skills/morning-briefing, .github/skills/morning-briefing and .opencode/skills/morning-briefing in your project.
What does Morning Briefing need to run?
SKILL.md names no scripts, command-line tools or credentials: Morning Briefing is instructions for the agent only.
Does Morning Briefing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Morning Briefing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Morning Briefing use?
Morning Briefing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Morning Briefing use?
About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Morning Briefing?
Skills that share tags, products or a category with Morning Briefing: Connect Apps with Composio (ComposioHQ/awesome-claude-skills, 77k stars), Superset Automate (superset-sh/superset, 15k stars), Composio Cloud Tools (quarqlabs/argus, 279 stars) and Executive Digest (mgonto/executive-assistant-skills, 118 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Morning Briefing?
TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 159 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.
Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.