- Home
- Skills
- Splitleaseteam
- Splitlease Monorepo
- Screenshot To Slack
screenshot-to-slack_skill
- JavaScript
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill splitleaseteam/splitlease_monorepo --skill screenshot-to-slack- SKILL.md3.2 KB
Overview
This skill captures screenshots with Playwright and uploads them to Slack with an optional comment and target channel. It supports capturing the current open page or navigating to a specified URL before taking the screenshot. The skill picks the appropriate Playwright MCP for dev vs. live and authenticated vs. guest contexts. After upload it returns the Slack message permalink for quick reference.
How this skill works
The skill parses a command with a URL (or "current"), optional channel, and optional comment. It selects the correct Playwright MCP based on the URL environment, takes a screenshot saved to a temp filename including a timestamp, and runs a script to upload the file to Slack. On success it reports the Slack message permalink; on failure it returns a clear error message and suggested remediation.
When to use it
- Share visual evidence of a bug found during testing or QA.
- Document the current page state for design or product review.
- Send automated screenshot reports as part of end-to-end test runs.
- Provide visual context during debugging discussions or incident triage.
- Quickly share a UI regression or layout issue with remote teams.
Best practices
- Specify channel explicitly to avoid posting to an unexpected default channel.
- Use the keyword "current" when you want to capture the already-open Playwright page without navigation.
- Include a brief, actionable comment describing what to look for in the screenshot.
- Choose the correct Playwright MCP for the environment: host vs guest and dev vs live.
- Clean up temporary screenshots after successful upload to free disk space.
Example use cases
- /screenshot-to-slack current — capture the active test page and post to the default Slack channel.
- /screenshot-to-slack https://example.com #qa "Header misalignment on Chrome" — navigate, capture, and comment.
- Automated test hook: run the skill after a failing E2E test to post visual evidence to #dev-alerts.
- Local dev check: /screenshot-to-slack http://localhost:8000 #dev "Search results after fix" using playwright-host-dev.
FAQ
SLACK_BOT_TOKEN is required. SLACK_DEFAULT_CHANNEL is optional and used if you don’t specify a channel.
What if I pass no URL and no page is open?
The skill will return an error asking you to provide a URL or open the target page first.
How do I get full-page screenshots?
Use the full-page option (e.g., --fullpage) when invoking the capture so Playwright saves the entire page.
What happens if upload fails?
The skill surfaces the Slack API error message and suggests checking the bot token, channel name, and network access.