Create a daily briefing combining changes in official Anthropic documentation with guide updates and CC CLI releases from the last 24 hours. Review added, removed, or modified sections alongside links to the original sources.
Daily update check — official Anthropic docs diff + guide/CC releases digest
Review the instructions the agent will receive before you install.
Use this skill when the user asks to run the migrated source command ccguide-daily.
Run this sequence in order. Present results as one consolidated report.
Call refresh_official_docs MCP tool to fetch the latest Anthropic docs and update the current snapshot.
If it fails (no baseline), tell the user to run /ccguide:init-docs once first, then stop.
Call diff_official_docs MCP tool to compare baseline vs refreshed current.
Call get_digest MCP tool with period: "day"
Present everything as a single daily briefing:
# Daily Codex Update — {today's date}
## Official Anthropic Docs
{diff results — added/removed/modified sections, or "No changes"}
## Guide + CC CLI
{digest results — guide CHANGELOG entries + CC releases from last 24h, or "No changes"}
---
Docs snapshot: {baseline date} → {current date}
Rules:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.
Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.
Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.
Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.
Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.
Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.