- Adds React 18 and 19 migration orchestration plugins
- Introduces comprehensive upgrade toolkits for migrating legacy React 16/17 and 18 codebases to React 18.3.1 and 19, respectively. Each plugin bundles specialized agents and skills for exhaustive audit, dependency management, class/component API migration, test suite transformation, and batching regression fixes.
- The React 18 toolkit targets class-component-heavy apps, ensures safe lifecycle and context transitions, resolves dependency blockers, and fully automates test migrations including Enzyme removal. The React 19 toolkit addresses breaking changes such as removal of legacy APIs, defaultProps on function components, and forwardRef, while enforcing a gated, memory-resumable migration pipeline.
- Both plugins update documentation, plugin registries, and skill references to support reliable, repeatable enterprise-scale React migrations.
* feat(orchestrator): add Discuss Phase and PRD creation workflow
- Introduce Discuss Phase for medium/complex objectives, generating context‑aware options and logging architectural decisions
- Add PRD creation step after discussion, storing the PRD in docs/prd.yaml
- Refactor Phase 1 to pass task clarifications to researchers
- Update Phase 2 planning to include multi‑plan selection for complex tasks and verification with gem‑reviewer
- Enhance Phase 3 execution loop with wave integration checks and conflict filtering
* feat(gem-team): bump version to 1.3.3 and refine description with Discuss Phase and PRD compliance verification
* chore(release): bump marketplace version to 1.3.4
- Update `marketplace.json` version from `1.3.3` to `1.3.4`.
- Refine `gem-browser-tester.agent.md`:
- Replace "UUIDs" typo with correct spelling.
- Adjust wording and formatting for clarity.
- Update JSON code fences to use ````jsonc````.
- Modify workflow description to reference `AGENTS.md` when present.
- Refine `gem-devops.agent.md`:
- Align expertise list formatting.
- Standardize tool list syntax with back‑ticks.
- Minor wording improvements.
- Increase retry attempts in `gem-browser-tester.agent.md` from 2 to 3 attempts.
- Minor typographical and formatting corrections across agent documentation.
* refactor: rename prd_path to project_prd_path in agent configurations
- Updated gem-orchestrator.agent.md to use `project_prd_path` instead of `prd_path` in task definitions and delegation logic.
- Updated gem-planner.agent.md to reference `project_prd_path` and clarify PRD reading.
- Updated gem-researcher.agent.md to use `project_prd_path` and adjust PRD consumption logic.
- Applied minor wording improvements and consistency fixes across the orchestrator, planner, and researcher documentation.
* feat(plugin): expand marketplace description, bump version to 1.4.0; revamp gem-browser-tester agent documentation with clearer role, expertise, and workflow specifications.
* chore: remove outdated plugin metadata fields from README.plugins.md and plugin.json
* feat(tooling): bump marketplace version to 1.5.0 and refine validation thresholds
- Update marketplace.json version from 1.4.0 to 1.5.0
- Adjust validation criteria in gem-browser-tester.agent.md to trigger additional tests when coverage < 0.85 or confidence < 0.85
- Refine accessibility compliance description, adding runtime validation and SPEC‑based accessibility notes- Add new gem-code-simplifier.agent.md documentation for code refactoring
- Update README and plugin metadata to reflect version change and new tooling
* docs: improve bug‑fix delegation description and delegation‑first guidance in gem‑orchestrator.agent.md
- Clarified the two‑step diagnostic‑then‑fix flow for bug fixes using gem‑debugger and gem‑implementer.
- Updated the “Delegation First” checklist to stress that **no** task, however small, should be performed directly by the orchestrator, emphasizing sub‑agent delegation and retry/escalation strategy.
* feat(gem-browser-tester): add flow testing support and refine workflow
- Update description to include “flow testing” and “user journey” among triggers.
- Expand expertise list to cover flow testing and visual regression.
- Revise knowledge sources and workflow to detail initialization, setup, flow execution, and teardown.
- Introduce comprehensive step types (navigate, interact, assert, branch, extract, wait, screenshot) with explicit wait strategies.
- Implement baseline screenshot comparison for visual regression.
- Restructure execution pattern to manage flow context and multi‑step user journeys.
* feat: add performance, design, responsive checks
* feat(styling): add priority-based styling hierarchy and validation rules
* feat: incorporate lint rule recommendations and update agent routing for ESLint rule handling
* chore(release): bump marketplace version to 1.5.4
* docs: Simplify readme
* chore: Add mobile specific agents and disable user invocation flags
* feat(architecture): add mobile agents and refactor diagram
* feat(readme): add recommended LLM column to agent team roles
* docs: Update readme
---------
Co-authored-by: Aaron Powell <me@aaron-powell.com>
* feat: add Salesforce Development plugin bundling Apex, Flow, LWC/Aura, and Visualforce agents
* feat: improve Salesforce plugin agents and add 3 quality skills
- Rewrote all 4 agent files with specific, actionable Salesforce guidance:
- salesforce-apex-triggers: added discovery phase, pattern selection matrix,
PNB test coverage standard, modern Apex idioms (safe nav, null coalescing,
WITH USER_MODE, Assert.*), TAF awareness, anti-patterns table with risks,
and structured output format
- salesforce-aura-lwc: major expansion — PICKLES methodology, data access
pattern selection table, SLDS 2 compliance, WCAG 2.1 AA accessibility
requirements, component communication rules, Jest test requirements, and
output format
- salesforce-flow: major expansion — automation tool confirmation step, flow
type selection matrix, bulk safety rules (no DML/Get Records in loops),
fault connector requirements, Transform element guidance, deployment
safety steps, and output format
- salesforce-visualforce: major expansion — controller pattern selection,
security requirements (CSRF, XSS, FLS/CRUD, SOQL injection), view state
management, performance rules, and output format
- Added 3 new skills to the plugin:
- salesforce-apex-quality: Apex guardrails, governor limit patterns, sharing
model, CRUD/FLS enforcement, injection prevention, PNB testing checklist,
trigger architecture rules, and code examples
- salesforce-flow-design: flow type selection, bulk safety patterns with
correct and incorrect examples, fault path requirements, automation density
checks, screen flow UX guidelines, and deployment safety steps
- salesforce-component-standards: LWC data access patterns, SLDS 2 styling,
accessibility (WCAG 2.1 AA), component communication, Jest requirements,
Aura event design, and Visualforce XSS/CSRF/FLS/view-state standards
- Updated plugin.json v1.0.0 → v1.1.0 with explicit agent paths and skill refs
* fix: resolve codespell error and README drift in Salesforce plugin
- Fix 'ntegrate' codespell false positive in salesforce-aura-lwc agent:
rewrote PICKLES acronym bullets from letter-prefixed (**I**ntegrate)
to full words (**Integrate**) so codespell reads the full word correctly
- Regenerate docs/README.plugins.md to match current build output
(table column padding was updated by the build script)
* fix: regenerate README after rebasing on latest staged
- **New skill: flowstudio-power-automate-monitoring** — flow health, failure
rates, maker inventory, Power Apps, environment/connection counts via
FlowStudio MCP cached store tools.
- **New skill: flowstudio-power-automate-governance** — 10 CoE-aligned
governance workflows: compliance review, orphan detection, archive scoring,
connector audit, notification management, classification/tagging, maker
offboarding, security review, environment governance, governance dashboard.
- **Updated flowstudio-power-automate-debug** — purely live API tools (no
store dependencies), mandatory action output inspection step, resubmit
clarified as working for ALL trigger types.
- **Updated flowstudio-power-automate-build** — Step 1 uses list_live_flows
(not list_store_flows) for the duplicate check, resubmit-first testing.
- **Updated flowstudio-power-automate-mcp** — store tool catalog, response
shapes verified against real API calls, set_store_flow_state shape fix.
- Plugin version bumped to 2.0.0, all 5 skills listed in plugin.json.
- Generated docs regenerated via npm start.
All response shapes verified against real FlowStudio MCP API calls.
All 10 governance workflows validated with real tenant data.
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Adds plugins/ember/ with plugin.json and README.md so Ember
appears as an installable plugin in the awesome-copilot
marketplace. The agent and skill files already exist at the
repo root from PR #1324.
Ran npm run plugin:validate (passes) and npm start to
regenerate README and marketplace.json.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add 9 Arize LLM observability skills
Add skills for Arize AI platform covering trace export, instrumentation,
datasets, experiments, evaluators, AI provider integrations, annotations,
prompt optimization, and deep linking to the Arize UI.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* Add 3 Phoenix AI observability skills
Add skills for Phoenix (Arize open-source) covering CLI debugging,
LLM evaluation workflows, and OpenInference tracing/instrumentation.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* Ignoring intentional bad spelling
* Fix CI: remove .DS_Store from generated skills README and add codespell ignore
Remove .DS_Store artifact from winmd-api-search asset listing in generated
README.skills.md so it matches the CI Linux build output. Add queston to
codespell ignore list (intentional misspelling example in arize-dataset skill).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* Add arize-ax and phoenix plugins
Bundle the 9 Arize skills into an arize-ax plugin and the 3 Phoenix
skills into a phoenix plugin for easier installation as single packages.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* Fix skill folder structures to match source repos
Move arize supporting files from references/ to root level and rename
phoenix references/ to rules/ to exactly match the original source
repository folder structures.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* Fixing file locations
* Fixing readme
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* feat(orchestrator): add Discuss Phase and PRD creation workflow
- Introduce Discuss Phase for medium/complex objectives, generating context‑aware options and logging architectural decisions
- Add PRD creation step after discussion, storing the PRD in docs/prd.yaml
- Refactor Phase 1 to pass task clarifications to researchers
- Update Phase 2 planning to include multi‑plan selection for complex tasks and verification with gem‑reviewer
- Enhance Phase 3 execution loop with wave integration checks and conflict filtering
* feat(gem-team): bump version to 1.3.3 and refine description with Discuss Phase and PRD compliance verification
* chore(release): bump marketplace version to 1.3.4
- Update `marketplace.json` version from `1.3.3` to `1.3.4`.
- Refine `gem-browser-tester.agent.md`:
- Replace "UUIDs" typo with correct spelling.
- Adjust wording and formatting for clarity.
- Update JSON code fences to use ````jsonc````.
- Modify workflow description to reference `AGENTS.md` when present.
- Refine `gem-devops.agent.md`:
- Align expertise list formatting.
- Standardize tool list syntax with back‑ticks.
- Minor wording improvements.
- Increase retry attempts in `gem-browser-tester.agent.md` from 2 to 3 attempts.
- Minor typographical and formatting corrections across agent documentation.
* refactor: rename prd_path to project_prd_path in agent configurations
- Updated gem-orchestrator.agent.md to use `project_prd_path` instead of `prd_path` in task definitions and delegation logic.
- Updated gem-planner.agent.md to reference `project_prd_path` and clarify PRD reading.
- Updated gem-researcher.agent.md to use `project_prd_path` and adjust PRD consumption logic.
- Applied minor wording improvements and consistency fixes across the orchestrator, planner, and researcher documentation.
* feat(plugin): expand marketplace description, bump version to 1.4.0; revamp gem-browser-tester agent documentation with clearer role, expertise, and workflow specifications.
* chore: remove outdated plugin metadata fields from README.plugins.md and plugin.json
* feat(tooling): bump marketplace version to 1.5.0 and refine validation thresholds
- Update marketplace.json version from 1.4.0 to 1.5.0
- Adjust validation criteria in gem-browser-tester.agent.md to trigger additional tests when coverage < 0.85 or confidence < 0.85
- Refine accessibility compliance description, adding runtime validation and SPEC‑based accessibility notes- Add new gem-code-simplifier.agent.md documentation for code refactoring
- Update README and plugin metadata to reflect version change and new tooling
* docs: improve bug‑fix delegation description and delegation‑first guidance in gem‑orchestrator.agent.md
- Clarified the two‑step diagnostic‑then‑fix flow for bug fixes using gem‑debugger and gem‑implementer.
- Updated the “Delegation First” checklist to stress that **no** task, however small, should be performed directly by the orchestrator, emphasizing sub‑agent delegation and retry/escalation strategy.
---------
Co-authored-by: Aaron Powell <me@aaron-powell.com>
* feat(orchestrator): add Discuss Phase and PRD creation workflow
- Introduce Discuss Phase for medium/complex objectives, generating context‑aware options and logging architectural decisions
- Add PRD creation step after discussion, storing the PRD in docs/prd.yaml
- Refactor Phase 1 to pass task clarifications to researchers
- Update Phase 2 planning to include multi‑plan selection for complex tasks and verification with gem‑reviewer
- Enhance Phase 3 execution loop with wave integration checks and conflict filtering
* feat(gem-team): bump version to 1.3.3 and refine description with Discuss Phase and PRD compliance verification
* chore(release): bump marketplace version to 1.3.4
- Update `marketplace.json` version from `1.3.3` to `1.3.4`.
- Refine `gem-browser-tester.agent.md`:
- Replace "UUIDs" typo with correct spelling.
- Adjust wording and formatting for clarity.
- Update JSON code fences to use ````jsonc````.
- Modify workflow description to reference `AGENTS.md` when present.
- Refine `gem-devops.agent.md`:
- Align expertise list formatting.
- Standardize tool list syntax with back‑ticks.
- Minor wording improvements.
- Increase retry attempts in `gem-browser-tester.agent.md` from 2 to 3 attempts.
- Minor typographical and formatting corrections across agent documentation.
* refactor: rename prd_path to project_prd_path in agent configurations
- Updated gem-orchestrator.agent.md to use `project_prd_path` instead of `prd_path` in task definitions and delegation logic.
- Updated gem-planner.agent.md to reference `project_prd_path` and clarify PRD reading.
- Updated gem-researcher.agent.md to use `project_prd_path` and adjust PRD consumption logic.
- Applied minor wording improvements and consistency fixes across the orchestrator, planner, and researcher documentation.
* feat(plugin): expand marketplace description, bump version to 1.4.0; revamp gem-browser-tester agent documentation with clearer role, expertise, and workflow specifications.
* chore: remove outdated plugin metadata fields from README.plugins.md and plugin.json
* Add roundup plugin: self-configuring status briefing generator
Adds a new plugin with two skills:
- roundup-setup: Interactive onboarding that learns the user's communication
style from examples, discovers available data sources, and builds audience
profiles. Writes a persistent config to ~/.config/roundup/config.md.
- roundup: Generates draft status briefings on demand by pulling from
configured sources (GitHub, M365, Slack, Google Workspace, etc.) and
synthesizing in the user's learned style for any defined audience.
Platform-agnostic by design -- adapts to whatever MCP tools are available
in the user's environment rather than assuming specific integrations.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Address PR review comments
- Fix 'use roundup' help text to clarify multi-audience behavior instead
of referencing a nonexistent 'default audience'
- Split bundled 'who do you report to + who is on your team' into two
separate ask_user questions per the one-question-at-a-time rule
- Specify ~/Desktop as explicit save path with fallback prompt when
directory doesn't exist
- Tables in README verified as correct markdown (single | delimiters)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Improve example-pasting UX in setup flow
- Make 'paste the whole thing right here' explicit so users aren't
unsure about what/how much to paste
- Confirm receipt more clearly ('grabbed all of that')
- Reframe second example prompt to explain why a second helps
- Cap follow-up asks at two so it doesn't feel nagging
- Note that messy formatting is fine
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Reinforce that more examples = better output
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* feat(orchestrator): add Discuss Phase and PRD creation workflow
- Introduce Discuss Phase for medium/complex objectives, generating context‑aware options and logging architectural decisions
- Add PRD creation step after discussion, storing the PRD in docs/prd.yaml
- Refactor Phase 1 to pass task clarifications to researchers
- Update Phase 2 planning to include multi‑plan selection for complex tasks and verification with gem‑reviewer
- Enhance Phase 3 execution loop with wave integration checks and conflict filtering
* feat(gem-team): bump version to 1.3.3 and refine description with Discuss Phase and PRD compliance verification
* <think>The user wants me to generate a conventional format commit message based on the git diff output provided.
Let me analyze the changes:
1. **`.github/plugin/marketplace.json`**:
- Updated the "gem-team" plugin description to include "complexity-aware research, multi-plan selection for critical tasks"
- Updated version from "1.2.1" to "1.3.0"
2. **`agents/gem-browser-tester.agent.md`**:
- Added `<tools>` section with new tools: get_errors, mcp_io_github_chr_performance_start_trace, mcp_io_github_chr_performance_analyze_insight
- Modified the `<expertise>` section (moved closing tag)
- Updated `<input_format_guide>` to use proper JSON code block format
- Updated `<output_format_guide>` to add "needs_revision" status option and restructured JSON formatting
- Updated `<constraints>` section - significantly changed the guidelines
This appears to be an update to:
- Plugin marketplace version bump
- Browser tester agent improvements (new tools, updated workflow constraints, better formatting)
Let me generate a conventional commit message:
- Type: Could be "feat" for new features or "chore" for maintenance
- Scope: could be "marketplace" and "browser-tester"
- Message should describe the changes succinctly
Looking at the changes more carefully:
- Plugin version bump from 1.2.1 to 1.3.0 - this is a feature update
- New tools added to browser tester agent
- Updated constraints/workflow for browser tester
I'll create a commit message that captures the essence:
</think>
feat: update gem-team to v1.3.0 and enhance browser-tester agent
- Bump gem-team plugin version from 1.2.1 to 1.3.0 with updated description
- Add performance tracing and insight tools to browser-tester agent
- Refactor input/output format guides with proper JSON code blocks
- Update agent constraints with improved tool usage and batching guidelines
* fix: correct typo "suiteable" to "suitable" in agent documentation
* Source dataverse plugin from microsoft/Dataverse-skills
The Dataverse plugin was previously bundled locally with a single
mcp-configure skill. It is now sourced externally from
microsoft/Dataverse-skills, which provides the full skill set:
init, setup, metadata, python-sdk, solution, mcp-configure, and overview.
- marketplace.json: update dataverse entry to external source format
- external.json: add Dataverse entry alongside Azure
- plugins/dataverse/: remove local plugin directory (now external)
- skills/mcp-configure/: remove top-level copy (now in external plugin)
- docs/README.plugins.md: update dataverse row with external link
- docs/README.skills.md: note mcp-configure moved to external plugin
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Make dataverse plugin docs generic to avoid stale counts
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Remove mcp-configure from skills index — now in external plugin
External plugins don't list their skills in README.skills.md
(consistent with azure-skills).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Revert manual edits to generated files
marketplace.json, README.plugins.md, and README.skills.md are
auto-generated. External plugins are discovered via external.json
and merged into marketplace.json by generate-marketplace.mjs.
Matches the Azure external plugin pattern — no manual doc entries.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Regenerate marketplace.json and docs after external plugin change
Run npm run build to pick up the new external dataverse entry and
remove the old local one from generated files.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* Add doublecheck plugin: three-layer verification pipeline for AI output
Adds a new plugin that helps users verify AI-generated content before
acting on it. Designed for sensitive contexts (legal, medical, financial,
compliance) where hallucinations carry real consequences.
Three verification layers:
- Self-Audit: extracts verifiable claims, checks internal consistency
- Source Verification: web searches per claim, produces URLs for human review
- Adversarial Review: assumes errors exist, checks hallucination patterns
Supports persistent mode (auto-verifies every factual response inline)
and one-shot mode (full report on specific text). Confidence ratings:
VERIFIED, PLAUSIBLE, UNVERIFIED, DISPUTED, FABRICATION RISK.
Includes:
- Skill (skills/doublecheck/) with bundled report template
- Agent (agents/doublecheck.agent.md) for interactive verification
- Plugin package (plugins/doublecheck/) bundling both
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Address review: fix tools YAML format, remove materialized artifacts
- Fix tools frontmatter in agents/doublecheck.agent.md to use standard
YAML list format instead of flow sequence with trailing comma
- Remove plugins/doublecheck/agents/ and plugins/doublecheck/skills/
from tracking; these paths are in .gitignore as CI-materialized
artifacts that should not be committed
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add napkin plugin: visual whiteboard collaboration for Copilot CLI
Napkin opens an interactive HTML whiteboard in the user's browser where
they can draw, sketch, and add sticky notes. When ready, they click
'Share with Copilot' which exports a PNG snapshot. The Copilot CLI agent
reads the PNG via the view tool, and the multimodal AI model interprets
the drawings, spatial layout, and text content — responding
conversationally as a collaborator.
Built for non-technical users: lawyers, PMs, business stakeholders,
designers, and anyone who thinks better visually.
Includes:
- Self-contained HTML whiteboard (zero external dependencies)
- Shape recognition (wobbly shapes snap to clean versions)
- Freehand drawing, sticky notes, arrows, text labels
- Auto-save to localStorage
- SKILL.md with agent instructions
- SVG visual guides for step-by-step README documentation
- Plugin manifest for Copilot CLI installation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix review feedback: roundRect compat, cross-platform shortcuts, eraser undo
- Add safeRoundRect() fallback for browsers without CanvasRenderingContext2D.roundRect()
- Update undo/redo button titles to show Ctrl/Cmd instead of Mac-only Cmd
- Fix eraser undo by capturing state before first erase mutation per gesture
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Update skills/napkin/templates/napkin.html
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Update plugins/napkin/README.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Update skills/napkin/templates/napkin.html
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Update skills/napkin/templates/napkin.html
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Update skills/napkin/templates/napkin.html
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Add missing Line (L) and Eraser (E) keyboard shortcuts to README
The in-app shortcuts panel and keyMap handler both support L for Line
and E for Eraser, but the README keyboard shortcuts table was missing
both entries. Adds them to match the actual implementation.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Combine docs/ and templates/ into assets/ per agentskills.io spec
Moves skills/napkin/docs/*.svg and skills/napkin/templates/napkin.html
into skills/napkin/assets/ to align with the Agent Skills specification.
Updates all path references in SKILL.md, README.md, and generated docs.
Addresses review feedback from PR #929.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Dan Velton <dvelton@Dans-MacBook-Pro.local>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Add automate-this plugin: screen recording to automation scripts
New plugin that analyzes screen recordings of manual processes and
proposes working automation scripts at multiple complexity tiers.
Features:
- Frame extraction via ffmpeg for visual process reconstruction
- Optional audio transcription via Whisper for narrated recordings
- Environment fingerprinting to constrain proposals to installed tools
- Application-specific automation strategies (browser, spreadsheet,
email, terminal, file management, macOS-native)
- Three-tier proposal system (quick win, full script, scheduled automation)
- Dry-run support for safe testing of all proposals
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Update skills/automate-this/SKILL.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Address code review feedback on automate-this plugin
- Fix privacy section: clarify that frames/audio are processed locally
but sent to the Copilot model for analysis (not purely local)
- Replace 'which' with 'command -v' for reliable tool detection with
explicit NO_FFMPEG/NO_WHISPER sentinels
- Use per-run secure temp directory (mktemp -d, mode 0700) instead of
fixed /tmp/ paths to prevent other users reading extracted frames
- Add -y flag and -loglevel warning to ffmpeg calls to prevent
overwrite prompts and avoid piping hiding exit codes
- Add whisper-cpp CLI invocation path so users who install only
whisper-cpp get working transcription
- Fix grouped command syntax in environment fingerprint to prevent
false 'not installed' fallthrough
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
- Make browser tester generic to support for chrome devotols mcp, playwright, agentic browser tools.
- Add Team lead and energetci peronsality to Orchestrator
- Add progress updates between phases/ waves
* Add azure-pricing plugin
* changes for azure pricing skill
* Remove plugin files, not part of this PR
* added changes for copilot estimator
* refactor: replace Playwright script with web fetch approach for Copilot Studio estimation
- Remove copilot-studio-estimator.py (Playwright browser automation)
- Update SKILL.md to instruct Copilot to fetch live billing rates from Microsoft docs URLs
- Keep COPILOT-STUDIO-RATES.md as cached fallback reference
- No Python dependencies needed — uses Copilot's built-in web fetch tool
* cleanup: remove estimator URL, mark rates as cached fallback
- Remove microsoft.github.io/copilot-studio-estimator from fetch URLs (React SPA, not fetchable)
- Mark billing rates table as dated cached snapshot with fallback notice
- Keep only Microsoft Learn URLs as live data sources
* fix: correct serviceName examples to match API values
* Update skills/azure-pricing/references/SERVICE-NAMES.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* chore: regenerate README.skills.md after build
* fix: remove URL triggering codespell false positive
* feat: add azure-pricing skill to azure-cloud-development plugin
---------
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* feat: Prd/ steer support
- Add supprot for PRD
- Vscode steer/ queue support
- Consistent artifacts
- Improved parallel running; for researchers too
* chore: improve prd update support
* chore: Make reviewer use prd for compaince
* chore: imrpvoe websearch in researcher
* fix(gem-team): revert gem-team plugin version from 1.5.0 to 1.2.0
Noob Mode is a plain-English translation layer for non-technical Copilot
CLI users (PMs, business stakeholders, designers, and anyone new to the
command line). When activated, it translates every approval prompt, error
message, and technical output into clear, jargon-free English with
color-coded risk indicators.
Includes:
- Standalone skill (skills/noob-mode/) with SKILL.md and bundled
glossary (100+ terms) and before/after examples
- Plugin (plugins/noob-mode/) for installation via
copilot plugin install noob-mode@awesome-copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Modified tools to make the agent more efficient
* Added skill for importing Azure Infrastructure as Code
* Updated readme
* Some wording improvements
* Added / to skills path endings
* ran npm start
The pcf-development plugin had no agents, skills, or commands
referenced - just an empty shell. Convert it to a proper skill
with comprehensive PCF development guidance.
Also resolve merge conflict in CONTRIBUTING.md.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Move plugin manifests from .github/plugin/ to .claude-plugin/
- Convert items[] to Claude Code spec fields (agents, commands, skills)
- Rename tags to keywords, drop display/featured/instructions from plugins
- Delete all symlinks and materialized files from plugin directories
- Add eng/materialize-plugins.mjs to copy source files into plugin dirs at publish time
- Add .github/workflows/publish.yml for staged->main publishing
- Update CI triggers to target staged branch
- Update validation, creation, marketplace, and README generation scripts
- Update CONTRIBUTING.md and AGENTS.md documentation
- Include all new content from main (polyglot-test-agent, gem-browser-tester,
fabric-lakehouse, fluentui-blazor, quasi-coder, transloadit-media-processing,
make-repo-contribution hardening, website logo/gradient changes)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Removed re-added collections/ path triggers from CI
- Merged plugin checklist improvements from both branches
- Kept plugin:generate-marketplace script from main
- Removed new ospo-sponsorship collection file (plugin already exists)
- Dropped obsolete plugin:migrate and plugin:refresh scripts
Replace Collections with Plugins as first-class citizens in the repo.
With the Copilot CLI v0.409 release making plugins an on-by-default
marketplace, collections are redundant overhead.
## What changed
### Plugin Infrastructure
- Created eng/validate-plugins.mjs (replaces validate-collections.mjs)
- Created eng/create-plugin.mjs (replaces create-collection.mjs)
- Enhanced all 42 plugin.json files with tags, featured, display, and
items metadata from their corresponding collection.yml files
### Build & Website
- Updated eng/update-readme.mjs to generate plugin docs
- Updated eng/generate-website-data.mjs to emit plugins.json with full
items array for modal rendering
- Renamed website collections page to plugins (/plugins/)
- Fixed plugin modal to use <div> instead of <pre> for proper styling
- Updated README.md featured section from Collections to Plugins
### Documentation & CI
- Updated CONTRIBUTING.md, AGENTS.md, copilot-instructions.md, PR template
- Updated CI workflows to validate plugins instead of collections
- Replaced docs/README.collections.md with docs/README.plugins.md
### Cleanup
- Removed eng/validate-collections.mjs, eng/create-collection.mjs,
eng/collection-to-plugin.mjs
- Removed entire collections/ directory (41 .collection.yml + .md files)
- Removed parseCollectionYaml from yaml-parser.mjs
- Removed COLLECTIONS_DIR from constants.mjs
Closes#711
