daily-update-desktop
Skill0 starsChanged 5 months agoNo licenceView on GitHub
Generates a daily intelligence briefing for a company using Claude's built-in web search only — the web/Desktop counterpart of the daily-update skill, for environments with no local filesystem and no API keys. It takes the user's search context (an attached file, the project's instructions, or text pasted into the chat), researches recent competitor/regulatory/industry/macro developments with WebSearch, and writes a briefing covering a news summary, impact to company risk, and concrete mitigation steps — shown in the chat first, then optionally exported to a downloadable Word document. Use this skill whenever a Claude.ai web or Claude Desktop user asks for their "daily update", "daily briefing", "morning briefing", "today's report/digest", wants to "catch up on news relevant to the company", or asks to check on competitors, industry shifts, or regulatory developments that could affect the business — even if they don't say "daily update" by name.
- Reads credentials
In this repositoryOne other file it gives its agents.
- daily-updateSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
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
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.

