github-workflow-standards

Define GitHub workflow agent standards for authentication, Markdown/HTML output, and WCAG AA accessibility.

387|42|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Community-Access/accessibility-agents --skill github-workflow-standards-community-access
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-workflow-standards
Source: https://github.com/Community-Access/accessibility-agents/tree/main/.gemini/extensions/a11y-agents/skills/github-workflow-standards
Command: npx skills add https://github.com/Community-Access/accessibility-agents --skill github-workflow-standards-community-access

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill establishes comprehensive standards and best practices for all GitHub workflow agents, ensuring consistency, efficiency, and accessibility in automated GitHub operations.

Core Features & Use Cases

  • Standardized Authentication: Ensures agents correctly identify users and their workspace context.
  • Smart Defaults & Inference: Minimizes user input by intelligently inferring repository scope, date ranges, and search parameters.
  • Dual Output Formats: Guarantees all generated documents are available in both Markdown and accessible HTML.
  • Accessibility Compliance: Enforces strict HTML accessibility standards for screen reader compatibility.
  • Progress & Parallelism: Defines patterns for announcing progress and executing tasks in parallel for efficiency.
  • Use Case: When building a new agent to manage GitHub issues, this Skill provides the foundational rules for how it should authenticate, scope its searches, format its output, and communicate progress to the user.

Quick Start

Apply these standards when developing any new GitHub workflow agent.

Frequently Asked Questions about github-workflow-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make GitHub workflow agents accessible for screen readers?

To make GitHub workflow agents accessible, you must enforce WCAG AA standards for HTML output. This ensures screen-reader-compliant HTML by defining strict accessibility rules for all automated agent-generated documents.

What are the best practices for GitHub workflow agent authentication and repository discovery?

GitHub workflow agent best practices require standardized authentication to identify user workspace context, paired with smart defaults that automatically infer repository scope and search parameters to minimize required user input.

How do I generate dual Markdown and HTML output for automated GitHub tasks?

Generating dual Markdown and HTML output for GitHub tasks requires applying workflow agent standards that guarantee all created documents are formatted in both Markdown and accessible HTML simultaneously.

Can I use parallel execution and progress announcements in GitHub automation agents?

Yes, GitHub automation agents can use parallel execution by applying workflow standards that define specific patterns for announcing task progress and executing multiple operations concurrently for improved efficiency.

Do I need to manually specify search parameters for GitHub workflow agents?

No, GitHub workflow agents do not need manual search parameters because they utilize smart defaults and inference. This functionality intelligently scopes repository context, date ranges, and search parameters automatically.

What guidelines exist for error handling in GitHub automation agents?

GitHub automation agent error handling guidelines are established within workflow standards, providing foundational rules for intelligent agent behavior, output quality enforcement, and standardized error management during automated operations.