OpenClaw Design Audit
openclaw/clawhub
Audits OpenClaw frontend code and rendered pages for token misuse, reimplemented primitives, accessibility and responsive defects and off-brand copy, with an evidence-based report.
Daily GitHub briefing: issues, PRs, reviews, releases and discussions.
Install Daily Briefing
$ npx skills add Community-Access/accessibility-agents --skill daily-briefing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Community-Access/accessibility-agents daily-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/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/daily-briefing .claude/skills/daily-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 "daily-briefing" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/daily-briefing into .claude/skills/daily-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-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/Community-Access/accessibility-agents/tree/main/skills/daily-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 Community-Access/accessibility-agents --skill daily-briefing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Community-Access/accessibility-agents daily-briefing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/daily-briefing .agents/skills/daily-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 "daily-briefing" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/daily-briefing into .agents/skills/daily-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-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 Community-Access/accessibility-agents --skill daily-briefing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Community-Access/accessibility-agents daily-briefing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/daily-briefing .cursor/skills/daily-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 "daily-briefing" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/daily-briefing into .cursor/skills/daily-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-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/Community-Access/accessibility-agents.git --path skills/daily-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 Community-Access/accessibility-agents --skill daily-briefing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Community-Access/accessibility-agents daily-briefing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/daily-briefing .gemini/skills/daily-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 "daily-briefing" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/daily-briefing into .gemini/skills/daily-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-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 Community-Access/accessibility-agents daily-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 Community-Access/accessibility-agents --skill daily-briefing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/daily-briefing .github/skills/daily-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 "daily-briefing" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/daily-briefing into .github/skills/daily-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-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 Community-Access/accessibility-agents --skill daily-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 Community-Access/accessibility-agents daily-briefing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/daily-briefing .opencode/skills/daily-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 "daily-briefing" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/daily-briefing into .opencode/skills/daily-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "daily-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
daily-briefing- GitHub stars
- 423
- Token cost
- ~1.3k tokens
- SKILL.md length
- 589 words
- Files
- 4 (incl. references)
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Daily GitHub briefing: issues, PRs, reviews, releases and discussions.
- Works in 9 steps: Orchestrated Data Collection -- Pull… → Priority-First Organization --… → Dual-Format Briefing Documents --… → …
- Tasks that involve Accessibility
- SKILL.md covers Daily Briefing Agent, Core Capabilities, Behavioral Rules and Reference files, plus 1 more section
- Calls node
What it does
Daily Briefing is an agent skill from Community-Access/accessibility-agents. Daily GitHub briefing: issues, PRs, reviews, releases and discussions.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/intelligence-layer.md` and `references/workflow.md`).
It sits in Frontend & Design, covering Accessibility. It works with GitHub. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.
When your agent uses it
- Tasks that involve Accessibility
Example prompts
- “/daily-briefing”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Orchestrated Data Collection -- Pull data from issues, PRs, reviews, notifications, releases, discussions, reactions, and accessibility…
- Priority-First Organization -- Everything sorted by urgency, not recency. What needs action right now surfaces first.
- Dual-Format Briefing Documents -- Generate both markdown and HTML files saved to the workspace. HTML is screen reader optimized with…
- Incremental Updates -- Run again later in the day to catch what changed since the morning briefing.
- Accessibility Tracking -- Include the latest VS Code Insiders and Stable accessibility changes as a dedicated section.
- Release Awareness -- Surface upcoming releases, recently shipped versions, and which PRs/issues are release-bound.
- Community Pulse -- Show reactions and sentiment on items to highlight what the community cares about.
- Discussion Monitoring -- Include active GitHub Discussions alongside issues and PRs.
- Reflection & Guidance -- End each briefing with patterns noticed and suggestions for the user's workflow.
What it can do on your machine
Read from SKILL.md and the folder at commit decf6ba. 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
Shell commands in SKILL.md call:
node
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
Daily Briefing loads about 1.3k tokens when it runs, and up to ~9.2k if it reads all its reference files. Until then it costs about 21 tokens; SKILL.md has 589 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 Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 589 words, ~1,272 tokens.
Download SKILL.mdSave it as
.claude/skills/daily-briefing/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- daily-briefing
- description
- Daily GitHub briefing: issues, PRs, reviews, releases and discussions.
- license
- MIT
- disable-model-invocation
- true
- metadata.tier
- specialist
- metadata.domain
- github
- metadata.output
- report
- metadata.effort
- medium
- metadata.title
- Daily Briefing
Daily Briefing Agent
Skills: github-workflow-standards, github-scanning, github-analytics-scoring, github-a11y-scanner, lighthouse-scanner
You are the user's daily GitHub command center -- the first thing they open each morning (or multiple times a day) to get a complete, prioritized picture of everything happening across their GitHub world. You orchestrate the other agents to build a single, comprehensive briefing document that can be reviewed, annotated, and acted on throughout the day.
Think of yourself as a chief of staff who prepares a daily intelligence brief: concise, prioritized, with clear action items and nothing important missed.
Critical: You MUST generate both a .md and .html version of every briefing document. Follow the dual output and accessibility standards in shared-instructions.md.
Core Capabilities
- Orchestrated Data Collection -- Pull data from issues, PRs, reviews, notifications, releases, discussions, reactions, and accessibility updates in one sweep.
- Priority-First Organization -- Everything sorted by urgency, not recency. What needs action right now surfaces first.
- Dual-Format Briefing Documents -- Generate both markdown and HTML files saved to the workspace. HTML is screen reader optimized with landmarks, skip links, and proper semantics.
- Incremental Updates -- Run again later in the day to catch what changed since the morning briefing.
- Accessibility Tracking -- Include the latest VS Code Insiders and Stable accessibility changes as a dedicated section.
- Release Awareness -- Surface upcoming releases, recently shipped versions, and which PRs/issues are release-bound.
- Community Pulse -- Show reactions and sentiment on items to highlight what the community cares about.
- Discussion Monitoring -- Include active GitHub Discussions alongside issues and PRs.
- Reflection & Guidance -- End each briefing with patterns noticed and suggestions for the user's workflow.
Show full SKILL.md (321 more words)Show less
Behavioral Rules
- Check workspace context first. Look for scan config files (
.a11y-*-config.json) and previous audit reports in the workspace root. - Run Batch 1 streams in parallel. Issues, PRs, CI/security, and accessibility scan streams run simultaneously - never serially.
- Announce every stream with / as it starts and completes. The user should always know what's being collected.
- Priority score before presenting. Apply the
github-analytics-scoringscoring formula to all issues and PRs before sorting or displaying them. - Dual output always. Every briefing document is saved as both
.mdand.htmlwith full accessibility standards. - Never overwrite today's briefing. If a briefing already exists for today, offer incremental update mode - show what changed, not a full regeneration.
- Workload analysis is mandatory. Every briefing ends with a light/heavy/release-crunch assessment and the top 3 recommended actions.
- Community pulse every briefing. Surface the single most-reacted item across repos.
- Streak tracking when available. Reinforce positive patterns (response rate, shipping velocity, clean backlog).
- Preferences from preferences.md. Respect
briefing.sectionsandbriefing.repossettings - don't ask for what's already configured. - Cross-reference intelligently. Linked PRs/issues, potential conflicts, and release context surface automatically without being asked.
- Never post status updates without request. Briefing is read-only by default - any GitHub action requires explicit user instruction.
- Reflection prompts on weekly. End-of-week briefings include a reflection prompt summarizing the week's impact.
- Section depth from config. Respect per-section depth settings (e.g.,
issues.limit,prs.days) from preferences.md. - Never truncate without saying so. If results are capped, state the limit and offer to expand.
Reference files
Read one only when the task reaches it. Do not read them all up front.
references/workflow.md- Workflowreferences/intelligence-layer.md- Intelligence Layer
Output contract
Collect findings as JSON from each specialist you dispatch, write them to
.a11y-history/<timestamp>/, then render the report with
node skills/a11y-core/scripts/render-report.mjs. Do not type the report by hand.
Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md.
Authoritative specifications for this skill: skills/a11y-core/references/sources.md.
© Community-Access, 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 3 other files (references) in skills/daily-briefing of Community-Access/accessibility-agents.
- SKILL.md
- agents/openai.yaml
- references/intelligence-layer.md
- references/workflow.md
Open the folder on GitHubat commit decf6ba
Compare with similar skills
Daily 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 |
|---|---|---|---|---|---|---|
| Daily Briefing this skillCommunity-Access/accessibility-agents | 423 | — | ~1.3k | Automated safety check: Pass | MIT | |
| OpenClaw Design Auditopenclaw/clawhub | 9.5k | — | ~498 | Automated safety check: Pass | MIT | |
| Bdgszymdzum/browser-debugger-cli | 172 | — | ~3.3k | Automated safety check: Notes | MIT | |
| Apple Notes Install Authjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Vitemagnus919/agent-skills | 115 | — | ~1.5k | Automated safety check: Notes | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None |
Similar skills
Bdg
szymdzum/browser-debugger-cli
Use bdg CLI to drive and debug a real Chrome via Chrome DevTools Protocol - navigate, click, fill and submit forms, check what an action changed (navigation, new messages, pending requests), inspect…
Apple Notes Install Auth
jeremylongshore/tons-of-skills-marketplace
Set up macOS automation access for Apple Notes via AppleScript, JXA, and Shortcuts.
Vite
magnus919/agent-skills
Operate Vite projects: inspect versions and configuration, run bounded development and production builds, diagnose dependency and asset failures, and configure environment-aware frontend delivery.
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
More from Community-Access/accessibility-agents
All 108 skills in this repoA11y Core
Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.
Kb Web Scanning
Community-Access/accessibility-agents
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Accessibility Lead
Community-Access/accessibility-agents
Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.
Alt Text Headings
Community-Access/accessibility-agents
Alt text, SVGs, figures, charts, heading order, page titles and landmarks.
Aria Specialist
Community-Access/accessibility-agents
ARIA roles, states and properties for custom widgets and dynamic content.
Cognitive Accessibility
Community-Access/accessibility-agents
Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.
Related
Works with
Questions about Daily Briefing
What does Daily Briefing do?
Daily GitHub briefing: issues, PRs, reviews, releases and discussions. Daily Briefing is an agent skill from Community-Access/accessibility-agents. Daily GitHub briefing: issues, PRs, reviews, releases and discussions.
When should I use Daily Briefing?
Daily Briefing fits situations like: tasks that involve Accessibility.
How do I install Daily Briefing in Claude Code?
Run `npx skills add Community-Access/accessibility-agents --skill daily-briefing -a claude-code`. Or copy the skill folder (skills/daily-briefing in Community-Access/accessibility-agents) into .claude/skills/daily-briefing in your project. Claude Code loads it when a task matches its description.
How do I install Daily Briefing in Codex?
Run `npx skills add Community-Access/accessibility-agents --skill daily-briefing -a codex`. Or copy the skill folder (skills/daily-briefing in Community-Access/accessibility-agents) into .agents/skills/daily-briefing in your project. Codex loads it when a task matches its description.
Can I use Daily 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 Community-Access/accessibility-agents --skill daily-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/daily-briefing, .gemini/skills/daily-briefing, .github/skills/daily-briefing and .opencode/skills/daily-briefing in your project.
What does Daily Briefing need to run?
Going by SKILL.md and its folder, Daily Briefing needs the command-line tools its instructions call (node).
Does Daily 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 Daily 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 Daily Briefing use?
Daily Briefing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Daily Briefing use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8k tokens, read only when the agent opens those files.
What are the alternatives to Daily Briefing?
Skills that share tags, products or a category with Daily Briefing: OpenClaw Design Audit (openclaw/clawhub, 9.5k stars), Bdg (szymdzum/browser-debugger-cli, 172 stars), Apple Notes Install Auth (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Vite (magnus919/agent-skills, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Daily Briefing?
Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 423 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.
Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.