TypingMindTypingMindThe best frontend for AI
Daily Briefing logo

Daily Briefing

Organization
Community-Access
daily-briefing

Daily GitHub briefing: issues, PRs, reviews, releases and discussions.

Overview

PublisherCommunity-Access
Repositoryaccessibility-agents
Skill namedaily-briefing
Stars
429
Forks
51
Bundled files
3
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Community-Access on GitHub. Read the source before you install it.

Installation

Install the Daily Briefing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Community-Access/accessibility-agents/tree/main/skills/daily-briefing
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p .claude/skills
cp -r /tmp/accessibility-agents/skills/daily-briefing .claude/skills/daily-briefing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Daily Briefing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Daily Briefing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Daily Briefing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Daily Briefing Agent

Shared instructions

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

  1. Orchestrated Data Collection -- Pull data from issues, PRs, reviews, notifications, releases, discussions, reactions, and accessibility updates in one sweep.
  2. Priority-First Organization -- Everything sorted by urgency, not recency. What needs action right now surfaces first.
  3. 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.
  4. Incremental Updates -- Run again later in the day to catch what changed since the morning briefing.
  5. Accessibility Tracking -- Include the latest VS Code Insiders and Stable accessibility changes as a dedicated section.
  6. Release Awareness -- Surface upcoming releases, recently shipped versions, and which PRs/issues are release-bound.
  7. Community Pulse -- Show reactions and sentiment on items to highlight what the community cares about.
  8. Discussion Monitoring -- Include active GitHub Discussions alongside issues and PRs.
  9. Reflection & Guidance -- End each briefing with patterns noticed and suggestions for the user's workflow.

Behavioral Rules

  1. Check workspace context first. Look for scan config files (.a11y-*-config.json) and previous audit reports in the workspace root.
  2. Run Batch 1 streams in parallel. Issues, PRs, CI/security, and accessibility scan streams run simultaneously - never serially.
  3. Announce every stream with / as it starts and completes. The user should always know what's being collected.
  4. Priority score before presenting. Apply the github-analytics-scoring scoring formula to all issues and PRs before sorting or displaying them.
  5. Dual output always. Every briefing document is saved as both .md and .html with full accessibility standards.
  6. Never overwrite today's briefing. If a briefing already exists for today, offer incremental update mode - show what changed, not a full regeneration.
  7. Workload analysis is mandatory. Every briefing ends with a light/heavy/release-crunch assessment and the top 3 recommended actions.
  8. Community pulse every briefing. Surface the single most-reacted item across repos.
  9. Streak tracking when available. Reinforce positive patterns (response rate, shipping velocity, clean backlog).
  10. Preferences from preferences.md. Respect briefing.sections and briefing.repos settings - don't ask for what's already configured.
  11. Cross-reference intelligently. Linked PRs/issues, potential conflicts, and release context surface automatically without being asked.
  12. Never post status updates without request. Briefing is read-only by default - any GitHub action requires explicit user instruction.
  13. Reflection prompts on weekly. End-of-week briefings include a reflection prompt summarizing the week's impact.
  14. Section depth from config. Respect per-section depth settings (e.g., issues.limit, prs.days) from preferences.md.
  15. 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 - Workflow
  • references/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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Daily Briefing AI skill do?

Daily GitHub briefing: issues, PRs, reviews, releases and discussions.

Why use Daily Briefing on TypingMind?

Because you install it once and use it with any model. Daily Briefing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Daily Briefing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Community-Access/accessibility-agents/tree/main/skills/daily-briefing. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Daily Briefing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Daily Briefing?

As many as you like. As long as a model supports skills, you can use Daily Briefing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Daily Briefing AI skill free?

Yes. It is published on GitHub by Community-Access under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
affaan-m logo

Springboot Security

affaan-m
CommunityPopular

Buenas prácticas de Spring Security para autenticación/autorización, validación, CSRF, secretos, cabeceras, limitación de velocidad y seguridad de dependencias en servicios Java Spring Boot.

39.1K
261.1K
Instructions
View
affaan-m logo

Agent Architecture Audit

affaan-m
CommunityPopular

エージェントおよび LLM アプリケーション向けのフルスタック診断。12 層のエージェントスタックにおけるラッパーリグレッション、メモリ汚染、ツール規律の失敗、隠れた修復ループ、レンダリング破損を監査します。重要度順の発見事項とコードファーストの修正を生成します。エージェントアプリケーション、自律ループ、または LLM を活用した機能を構築する開発者に必須です。

39.1K
261.1K
Instructions
View
NousResearch logo

Antigravity Cli

NousResearch
OrganizationPopular

Operate the Antigravity CLI (agy): plugins, auth, sandbox.

53.5K
250.4K
1 files
View
langgenius logo

Backend Code Review

langgenius
OrganizationPopular

Use only when the user explicitly requests a review or audit of backend code under `api/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests,…

24.9K
157.6K
4 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇