Run any Skill in Manus with one click

owpenbot-test

Stars24

Forks9

UpdatedFebruary 11, 2026 at 01:43

Run owpenbot/openwrk integration tests with Telegram test tokens. Triggers when user mentions: - "owpenbot tests" - "telegram test tokens" - "openwrk integration test"

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

different-ai

different-ai/openwork-hub

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

4 files

SKILL.md

readonly

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"

Quick Usage (Already Configured)

Run owpenbot + openwrk tests

skills/owpenbot-test/scripts/run-tests.sh

First-Time Setup (If Not Configured)

Copy skills/owpenbot-test/.env.example to skills/owpenbot-test/.env.
Fill in:
- OWPENBOT_TEST_TOKEN_ENV
- OWPENBOT_TEST_TOKEN_CLI
- (Optional) OWPENBOT_DIR and OPENWORK_DIR to override auto-detection.
Run the script above.

Common Gotchas

.env is optional but ignored by git; tokens should stay local.
The script will auto-detect repos under _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.

More from this repository

same repository

agent-creator

different-ai/openwork-hub

Create new OpenCode agents with a gpt-5.2-codex default.

2026-02-1124

command-creator

different-ai/openwork-hub

Create OpenCode custom commands for repeatable tasks.

2026-02-1124

create-cal-com-link

different-ai/openwork-hub

Create targeted Cal links for specific people or teams

2026-02-1124

openwork-chrome-mcp-testing

different-ai/openwork-hub

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"

2026-02-1124

openwork-docker-chrome-mcp

different-ai/openwork-hub

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"

2026-02-1124

plugin-creator

different-ai/openwork-hub

Create OpenCode plugins and know where to load them.

2026-02-1124

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"

Quick Usage (Already Configured)

Run owpenbot + openwrk tests

skills/owpenbot-test/scripts/run-tests.sh

First-Time Setup (If Not Configured)

Copy skills/owpenbot-test/.env.example to skills/owpenbot-test/.env.
Fill in:
- OWPENBOT_TEST_TOKEN_ENV
- OWPENBOT_TEST_TOKEN_CLI
- (Optional) OWPENBOT_DIR and OPENWORK_DIR to override auto-detection.
Run the script above.

Common Gotchas

.env is optional but ignored by git; tokens should stay local.
The script will auto-detect repos under _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.