testing-blocks
Skill from adobe/skills
Install
npx skills add adobe/skills --skill testing-blocks
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-official
/plugin install aem-edge-delivery-services@adobe-skills
This skill is part of the plugin “aem-edge-delivery-services”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the testing-blocks skill do?
Description from the SKILL.md in the source repository.
Questions about testing-blocks
What does the testing-blocks skill do?
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
How do I install testing-blocks?
In a terminal: npx skills add adobe/skills --skill testing-blocks. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use testing-blocks?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is testing-blocks safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from adobe/skills
Expert guidance for architecting and troubleshooting Adobe Workfront Planning (WFP, aka "Maestro"): workspace and record-type design, record connections and hierarchies, formula fields, object and connection limits across Select/Prime/Ultimate tiers, the Planning API …
Review an exported Adobe Workfront Planning + Fusion scenario blueprint (.json) for performance, speed, resource use, and API call volume, and produce a prioritized optimization self-review.
Discover and collect all URLs of a website with the web CLI: parses robots.txt and sitemaps (XML, sitemap indexes, gzip) or follows links, with include/exclude glob patterns, a URL limit and language …
Captures the rendered layout of a webpage as a spatial tree of elements, with positions, sizes, grid layouts, backgrounds, and overlay occlusion, via the web CLI.
Reduces a webpage to a structural skeleton. The web CLI detects sections and replaces content with semantic tokens (text, headings, images, CTAs, links, inputs), then the agent collapses repeated patterns and decorative …
Detects and removes overlays that block a webpage (cookie and GDPR consent banners, modals, newsletter popups, paywalls, login walls) with the web CLI, using Consent-O-Matic rules for known consent platforms plus DOM …
Detects the languages on a webpage, both declared in markup (html lang, hreflang links, nested lang attributes, Content-Language meta) and present in the body text (Google CLD3), and reports where the two …
Extracts structured resources from a webpage with the web CLI: icons (SVGs classified as icon or logo and optimized for AEM Edge Delivery Services /icons/), metadata and Open Graph tags, body text …
Related skills in Testing & QA
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any …
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Automate browser interactions, test web pages and work with Playwright tests.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.