// Run owpenbot/openwrk integration tests with Telegram test tokens. Triggers when user mentions: - "owpenbot tests" - "telegram test tokens" - "openwrk integration test"
| name | owpenbot-test |
| description | Run owpenbot/openwrk integration tests with Telegram test tokens. Triggers when user mentions: - "owpenbot tests" - "telegram test tokens" - "openwrk integration test" |
skills/owpenbot-test/scripts/run-tests.sh
skills/owpenbot-test/.env.example to skills/owpenbot-test/.env.OWPENBOT_TEST_TOKEN_ENVOWPENBOT_TEST_TOKEN_CLIOWPENBOT_DIR and OPENWORK_DIR to override auto-detection..env is optional but ignored by git; tokens should stay local._repos/owpenbot and _repos/openwork if dirs are not set..env.example lists the minimum config required by the script.OWPENBOT_TEST_TOKEN_ENV is used by the CLI tests to seed Telegram config.Create new OpenCode agents with a gpt-5.2-codex default.
Create OpenCode custom commands for repeatable tasks.
Create targeted Cal links for specific people or teams
Use Chrome MCP to verify OpenWork UI flows, especially any feature that touches remote behavior. Triggers when user mentions: - "test with chrome mcp" - "ui verification" - "remote behavior test"
Start the OpenWork dev stack via Docker and verify real user flows via Chrome MCP. Triggers when user mentions: - "dev-up.sh" - "docker dev stack" - "verify in chrome mcp" - "test the real flow"
Create OpenCode plugins and know where to load them.