Find relevant Claude learning resources for an onboarding question.
Useful for learning a feature; it is outside the intended scope of an already active task.
Choose documented Claude Code skills and MCP servers for coding, documents, design, browser work and repository operations. Compare requirements and setup.
Claude Code skills and MCP servers add different capabilities. A skill describes a workflow and can package supporting resources. An MCP server exposes tools from a service or runtime. Begin with the task, then decide which kind of addition supplies what is missing.
| Task | Skills to inspect | MCP approach |
|---|---|---|
| Frontend implementation | Frontend Design, Web Artifacts Builder | Inspect tools required by your client |
| Browser workflow | Webapp Testing | Playwright MCP for a browser tool interface |
| Repository work | Task-specific development guidance | GitHub MCP Server for repository operations |
| Library references | Claude API for Anthropic integration work | Context7 for library documentation |
| Documents | DOCX, PDF, XLSX, PPTX | A document skill has its own dependencies |
The Webapp Testing skill and Playwright MCP are not the same installation. One supplies a testing process; the other supplies an MCP tool interface. Their comparison uses the same facts as the cards.
The selected skills come from the reviewed Anthropic examples. Read the actual skill folder, dependencies and license before installing it through the repository's documented Claude Code method. Review helper resources before execution.
For an MCP server, use its Claude Code-specific setup. Check the transport, account authorization and local runtime. A service connection does not itself provide the workflow instructions of a skill.
The compatibility in these cards is documented for the CLI surface. It is not automatically extended to every Claude interface. Claude access, API calls and connected services may have separate charges; unknown pricing stays unknown.
Inspect a representative result in your own environment before relying on the addition. The catalog reports documentation, not practical installations. Compare the skills and MCP servers or read how to choose between them.
Find relevant Claude learning resources for an onboarding question.
Useful for learning a feature; it is outside the intended scope of an already active task.
Prepare interactive generative graphics with repeatable random seeds.
Choose this for code-driven art; it requires a p5.js workflow rather than a general image editor.
Apply Anthropic visual identity to documents and other artifacts.
Its brand choices belong to Anthropic; adapt a separate skill for a different organization.
Guide the composition of static posters and visual artwork.
Intended for still visual deliverables rather than interactive application behavior.
Look up Claude API and SDK details while developing an integration.
This guidance targets Anthropic integration work; using an API can introduce separate usage charges.
Add focused questions that help a reader inspect an actionable answer.
Designed for selected advice and draft artifacts; routine code and trivial lookups are excluded.
Structure an iterative process for writing documentation with a collaborator.
Choose it when context and reader feedback are available; it is not a one-shot file converter.
Prepare and revise Word documents with deliberate document structure.
Targets Word files; PDF and spreadsheet workflows need their own skills and dependencies.
Guide visual direction and typography for a new or revised interface.
Focuses on visual design decisions; it does not independently verify application functionality.
Adapt internal updates to a consistent organizational format.
Requires the appropriate communication template and organization-specific context.
Guide the design of MCP tools for connecting an agent to a service.
A working integration still requires API access, implementation and verification of tool behavior.
Support extraction, assembly and editing tasks for PDF documents.
Scanned inputs can require OCR; inspect the skill dependencies and validate extracted results.
Create or revise presentation files, including slide structure and notes.
Targets PowerPoint files and templates; other deliverable formats use separate workflows.
Develop and evaluate a reusable skill for a specific workflow.
Meaningful evaluation requires representative tasks and success criteria supplied by the operator.
Prepare small animated assets suitable for sharing in Slack.
Output is an animated image; it does not post to Slack or configure a workspace.
Apply a coherent color and font theme to an existing artifact.
A theme changes presentation; it does not validate the artifact content or data.
Build interactive HTML artifacts with multiple frontend components.
Choose it for richer application structure; simple single-file artifacts are outside its intended focus.
Inspect a local web application with browser automation.
Needs an accessible local application and browser dependencies; it does not certify every target environment.
Prepare, repair or transform spreadsheet files and tabular deliverables.
A spreadsheet must be the main deliverable; document and Google Sheets API tasks need another workflow.
Connect an assistant to GitHub repository, issue and pull-request workflows.
Grant only the GitHub permissions your workflow needs; host authentication and repository access remain separate requirements.
Let an MCP client inspect and operate web pages with Playwright.
Requires a supported Node.js and browser environment; browser automation access needs deliberate permission controls.
Retrieve current library documentation for a coding workflow.
Authentication and rate limits depend on the selected setup; verify the current service plan before relying on sustained usage.