cabinet-automation

Evaluate automation resilience for web bots, scrapers, and API integrations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/orenmagid/claude-cabinet --skill cabinet-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cabinet-automation
Source: https://github.com/orenmagid/claude-cabinet/tree/main/templates/skills/cabinet-automation
Command: npx skills add https://github.com/orenmagid/claude-cabinet --skill cabinet-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automation cabinet members identify and evaluate the resilience of automated bots, scrapers, and scheduled tasks to withstand UI changes, anti-bot measures, and token expiries.

Core Features & Use Cases

  • Evaluate selector robustness and API reliance to minimize brittle automation.
  • Plan, audit, and execute improvements across browser automation, HTTP flows, and scheduling.
  • Apply to real-world scenarios like data scraping, price monitoring, and form automation across diverse target sites.

Quick Start

Follow the briefing and start an initial audit of your automation pipelines.

Frequently Asked Questions about cabinet-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit web scrapers for anti-bot detection and fragility?

To audit web scrapers for anti-bot fragility, evaluate selector robustness, API reliance, and token lifecycle handling to identify vulnerabilities across your automated pipelines. This process detects rate limiting, authentication expiry, and UI change risks in scheduled tasks.

Why does my Playwright automation break when session tokens expire?

Playwright automation breaks on token expiry without proper lifecycle handling. Hardening automation involves enforcing token lifecycle management and session reconstruction to maintain authenticated flows and recover gracefully from expiry errors.

How do I improve Playwright selector robustness for web automation?

To improve Playwright selector robustness, evaluate API reliance and minimize brittle UI dependencies during planning and audit phases. Implementing robust selectors and error recovery mechanisms ensures automation withstands target site UI changes.

Does this automation hardening approach work with HTTP integrations and scheduled tasks?

This automation hardening approach works with HTTP integrations and scheduled tasks by applying resilience evaluations across browser automation and HTTP flows. It detects rate limiting and authentication expiry across targets like data scraping and price monitoring.

What is the best way to handle rate limiting in API integrations and web scrapers?

The best way to handle rate limiting in API integrations and web scrapers is to audit automation resilience and enforce error recovery protocols. Planning improvements across HTTP flows and scheduling minimizes disruptions from anti-bot defenses and rate limits.