Loading...
Loading...
Found 482 Skills
Automate browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to: - Navigate websites and interact with web pages - Fill forms and click buttons - Take screenshots of web content - Test web applications - Extract information from web pages - Debug frontend issues in the browser - Monitor console logs and network requests - Record browser sessions as video This skill uses agent-browser for comprehensive browser automation. RECOMMENDATION: Disable Chrome DevTools or Playwright MCP when using this skill to save context.
Test local web applications with Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, or inspect browser logs.
Luban - Skill Polishing Workshop. Transform a "usable Skill" into a public Skill asset that is "understandable, installable, shareable, verifiable, and continuously evolvable". The methodology consists of five craftsman-like steps: 1. Material Inspection: First challenge whether the premise of this Skill is valid; directly state if the "material" is not worth polishing. 2. Peer Research: Search for similar Skills online to clarify its position in the ecosystem. 3. Dimension Measurement: Evaluate using three metrics - structure, actual testing, and live verification (live verification means reconciling with real running outputs; a green CI can be deceptive). 4. Iterative Refinement: Freeze the original version as a baseline; only retain changes that pass the verification gate, otherwise revert. Try to institutionalize verification methods as tools and rules in the repository. 5. Post-Release Iteration: Release is not the end; maintain a benchmark observation list, and start the next iteration based on real feedback. This tool is used when users want to upgrade, optimize, polish, productize, or release their self-developed Skills. The final deliverables include a structured Skill Polishing Report, directly replaceable rewritten segments, and a shareable "Graduation Certificate" result card that can be screenshot. Trigger phrases include but are not limited to: "Let Luban take a look at this skill", "Polish at Luban's Workshop", "Polish my skill", "Upgrade my skill", "Optimize this skill", "Skill check-up", "Skill audit", "Productize my skill", "How to release this skill", "Benchmark against similar skills", "Why no one installs my skill", "Help me publish my skill to GitHub/ClawHub", "Improve SKILL.md". Even if users only provide a Skill directory, GitHub repository link, or a segment of SKILL.md saying "Help me figure out how to modify it", it should be triggered as long as the context is about making the Skill more usable and shareable. Do NOT use this for creating a new Skill from scratch (use skill-creator), regular code review (use code-review), or rewriting ordinary prompts unrelated to Skill assets.
Browser automation via Playwright CLI. Open pages, interact with elements, take screenshots, and more. Ideal for coding agents and automated testing workflows.
Non-interactive X11 desktop control for AI agents. Use when the task involves controlling a Linux desktop - clicking, typing, reading windows, waiting for UI state, or taking screenshots inside a sandbox or VM.
Review ML or AI experiment figures, tables, plots, captions, result narratives, and paper visual style before they are shown in a paper, advisor meeting, report, slide deck, rebuttal, or submission. Use this skill whenever the user has experimental results, plots, tables, metrics, screenshots, captions, draft result sections, or wants to audit figure style choices such as color, typography, markers, symbols, line widths, sizing, and venue-consistent visual conventions.
Interact with an iOS simulator or Android emulator using argent MCP tools. Use when tapping UI elements, performing gestures, scrolling, typing text, pressing hardware buttons, launching apps, opening URLs, taking screenshots.
Analyze a completed Meticulous test run — fetch the diff summary, inspect representative screenshots, DOM diffs, and timelines. Accepts a test-run ID, a PR number (resolved against the local repo), or otherwise identifies the test-run ID from the local repo's current branch and its associated PR. Use when asked to review Meticulous test results, or while reviewing or babysitting a PR to assess and fix a failing Meticulous Tests CI check.
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
Canonical Playwright hub for E2E tests and ad-hoc browser automation. Use when the user explicitly mentions "Playwright", "@playwright/test", "npx playwright", "playwright.config.ts", "PWDEBUG", "trace viewer", or "toHaveScreenshot". Avoid using for generic browser automation unless Playwright is requested, and avoid using for pure web scraping.
Android device control and UI automation via ADB using a TypeScript helper CLI. Use for device/emulator discovery, USB or Wi-Fi connection, app launch/force-stop, tap/swipe/keyevent/text input, screenshots, APK install handling, device reset for app, and ADB troubleshooting. Use with ai-vision for screenshot-based UI recognition and coordinate decisions.