AgentStack
SKILL verified MIT Self-run

Do Wdr Assets

skill-d-oit-do-web-doc-resolver-do-wdr-assets · by d-oit

Create screenshots, images, and visual tests for documentation. Use when you need to capture UI screenshots, generate visual assets, create test captures, or update documentation images. Automates browser-based image capture with agent-browser and saves to assets/ folder.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-d-oit-do-web-doc-resolver-do-wdr-assets

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Do Wdr Assets? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

WDR Assets Skill

Automated screenshot and visual asset generation for documentation.

When to use this skill

Activate this skill when you need to:

  • Capture UI screenshots for documentation
  • Generate visual assets for README.md
  • Create test captures for release notes
  • Update documentation images
  • Take before/after screenshots for changes
  • Generate visual regression test baselines

Asset Structure

assets/
├── screenshots/
│   ├── homepage.png          # Main UI screenshot
│   ├── help-page.png         # Help page screenshot
│   ├── resolve-flow.png      # Resolution flow demo
│   ├── providers.png         # Provider list screenshot
│   └── release-vX.Y.Z/      # Version-specific captures
│       ├── homepage.png
│       └── new-feature.png
└── README.md                 # Asset documentation

Quick Start

Capture Homepage

# Open production site and capture
agent-browser open "https://web-eight-ivory-29.vercel.app"
agent-browser wait --load networkidle
agent-browser screenshot --full assets/screenshots/homepage.png
agent-browser close

Capture with Annotations

agent-browser open "https://web-eight-ivory-29.vercel.app"
agent-browser wait --load networkidle
agent-browser screenshot --annotate assets/screenshots/homepage-annotated.png
agent-browser close

Release Capture Workflow

# Create release folder
mkdir -p assets/screenshots/release-v$VERSION

# Capture all pages
./scripts/capture-release.sh $VERSION

Commands

capture

Capture a single page screenshot.

agent-browser open 
agent-browser wait --load networkidle
agent-browser screenshot assets/screenshots/.png
agent-browser close

capture-full

Capture full-page screenshot.

agent-browser open 
agent-browser wait --load networkidle
agent-browser screenshot --full assets/screenshots/.png
agent-browser close

capture-flow

Capture a multi-step flow with screenshots.

./scripts/capture-flow.sh 

capture-release

Capture all pages for a release.

./scripts/capture-release.sh 

Configuration

Viewport Settings

Default: 1280x720

agent-browser set viewport 1920 1080    # Desktop HD
agent-browser set viewport 375 812      # iPhone
agent-browser set viewport 1440 900    # Laptop

Screenshot Quality

agent-browser screenshot --screenshot-format jpeg --screenshot-quality 90

Integration with Docs

README.md Image References

Release Notes

## What's New in vX.Y.Z

Automation

Pre-commit Hook

Add to .git/hooks/pre-commit:

# Capture screenshots if UI files changed
if git diff --cached --name-only | grep -q "web/"; then
    ./scripts/capture-release.sh "pre-commit"
fi

CI/CD Pipeline

- name: Capture screenshots
  run: |
    npm run build
    npm run dev &
    ./scripts/capture-release.sh "ci-${{ github.sha }}"

Best Practices

  1. Consistent viewport: Use same viewport for comparable screenshots
  2. Wait for load: Always use wait --load networkidle before capture
  3. Version folders: Use release-vX.Y.Z/ for release captures
  4. Naming convention: Use kebab-case for filenames
  5. Full page: Use --full for documentation screenshots
  6. Annotated: Use --annotate for UI documentation

Related Skills

  • agent-browser: Browser automation
  • do-wdr-cli: Rust CLI for web resolution
  • do-web-doc-resolver: Python resolver

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.