Automated summary
Calls the coverage_summary MCP tool to produce a summary table of article, capability and functionality counts for a chosen pivot (scope, system or migration_state).
Strengths
- Single tool call that returns results already shaped as a 3-column table
- Three explicit analysis axes (scope, system, migration state) with concrete example values
- Asks the user which pivot to use when none is given, preventing ambiguous reports
Limitations
- Entirely dependent on the mcp__bigweld__coverage_summary tool being available
- Only returns aggregate counts, with no per-article detail or trend analysis
- The listed pivot values are specific to one migration context and need adapting elsewhere
When you need a fast aggregate view of documentation coverage ahead of a migration status meeting.
When you need line-level article detail or a comparison across time, neither of which the tool provides.
Security analysis
SafeThe skill only declares and calls a single read-only MCP tool (coverage_summary) to format a summary table. It contains no shell commands, network calls, file writes, credential handling, or obfuscated payloads, so there is no meaningful execution risk.
No concerns found
How this analysis is madeExamples
/rollup migration_state=gap/rollup scope=snow-targetGive me the coverage rollup — break it down by system.name: rollup description: Coverage summary — per-scope, per-system, or per-migration-state breakdown of article + capability + functionality counts. allowed-tools:
- "mcp__bigweld__coverage_summary"
/rollup [pivot]
Call coverage_summary() with the user's chosen pivot:
scope=<name>for per-scope breakdown (e.g.,sfdc-internal,snow-target,migration-mapping,pan-hpe)system=<name>for per-system breakdown (sfdc,snow,manual,tbd,shared)migration_state=<name>for per-state breakdown (current,target,gap,deprecated)
Present results as a 3-column table (Article / Capability / Functionality counts). Ask which pivot Alex wants if he didn't specify.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/coverage-summary-rollup-mrzxuq3b/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/coverage-summary-rollup-mrzxuq3b' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/coverage-summary-rollup-mrzxuq3b/download' --output '.skill-downloads/coverage-summary-rollup-mrzxuq3b/SKILL.md.part' && mv '.skill-downloads/coverage-summary-rollup-mrzxuq3b/SKILL.md.part' '.skill-downloads/coverage-summary-rollup-mrzxuq3b/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/coverage-summary-rollup-mrzxuq3b/SKILL.md' && test -s '.skill-downloads/coverage-summary-rollup-mrzxuq3b/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/rollup' && cp -R '.skill-downloads/coverage-summary-rollup-mrzxuq3b' '.claude/skills/rollup'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/coverage-summary-rollup-mrzxuq3b'openskills read 'coverage-summary-rollup-mrzxuq3b'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/coverage-summary-rollup-mrzxuq3b/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Supabase Docs Authoring
Documentation
Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.
Create Architecture Decision Record
Documentation
Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.
Plan update with deep research
Documentation
Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.