Agent skill

Test Platform Worker

by CorrectRoadH in CorrectRoadH/OpenTickly

Harden shared test infrastructure, runtime readiness, schema setup, and parallel lane behavior.

AGPL-3.0Auto-check passed

Install Test Platform Worker

skills CLI
$ npx skills add CorrectRoadH/OpenTickly --skill test-platform-worker -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install CorrectRoadH/OpenTickly test-platform-worker --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/CorrectRoadH/OpenTickly.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.factory/skills/test-platform-worker .claude/skills/test-platform-worker && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
test-platform-worker
GitHub stars
306
Token cost
~1.2k tokens
SKILL.md length
331 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Harden shared test infrastructure, runtime readiness, schema setup, and parallel lane behavior.

  • Works in 9 steps: Read mission.md, mission AGENTS.md,… → Confirm the feature’s boundary changes… → Reproduce the current blocker first with… → …
  • SKILL.md covers When to Use This Skill, Required Skills, Work Procedure and Example Handoff, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Test Platform Worker is an agent skill from CorrectRoadH/OpenTickly. Harden shared test infrastructure, runtime readiness, schema setup, and parallel lane behavior.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Self-hosted, Toggl-compatible time tracker. The licence is AGPL-3.0.

Example prompts

  • “/test-platform-worker”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Read mission.md, mission AGENTS.md, .factory/services.yaml, and .factory/library/*.md relevant to runtime/test topology.
  2. Confirm the feature’s boundary changes before editing anything: ports, schema path, queue prefix rules, CI/local runtime reuse, or…
  3. Reproduce the current blocker first with the canonical command from .factory/services.yaml.
  4. If the work touches backend/runtime/schema
  5. If the work touches website/browser runtime or browser-visible readiness
  6. Make the minimum infrastructure/config/code changes needed to unblock the shared path.
  7. Re-run the specific failing command(s), then run the broader shared checks affected by the feature.
  8. Update shared state if the feature proves factual runtime changes workers need (services.yaml, .factory/library/*, mission AGENTS.md if…
  9. In the handoff, be explicit about

What it can do on your machine

Read from SKILL.md and the folder at commit 5ffd0a0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Test Platform Worker loads about 1.2k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 331 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CorrectRoadH/OpenTickly at commit 5ffd0a0, republished under its AGPL-3.0 licence (© CorrectRoadH). 331 words, ~1,207 tokens.

Download SKILL.mdSave it as .claude/skills/test-platform-worker/SKILL.md (or your agent's skills folder).
name
test-platform-worker
description
Harden shared test infrastructure, runtime readiness, schema setup, and parallel lane behavior.

Test Platform Worker

NOTE: Startup and cleanup are handled by worker-base. This skill defines the work procedure.

When to Use This Skill

Use for features that change shared validation infrastructure: runtime readiness, pgschema environment projection, dedicated test-schema setup, browser-lane gating, CI/local test topology, and parallel execution policy.

Required Skills

  • vite-plus — use for repo-local JS/toolchain commands and website command execution.
  • agent-browser — use when validating browser startup, shell reachability, or HTTP/browser readiness for the website runtime.

Work Procedure

  1. Read mission.md, mission AGENTS.md, .factory/services.yaml, and .factory/library/*.md relevant to runtime/test topology.
  2. Confirm the feature’s boundary changes before editing anything: ports, schema path, queue prefix rules, CI/local runtime reuse, or readiness gates.
  3. Reproduce the current blocker first with the canonical command from .factory/services.yaml.
  4. If the work touches backend/runtime/schema:
    • keep local runtime on 8080
    • keep Postgres external on 5432
    • use pgschema as the only schema reconciliation path
    • never point tests at the development business schema
  5. If the work touches website/browser runtime or browser-visible readiness:
    • keep local runtime on 5173
    • validate readiness with an actual HTTP probe, not logs
    • use agent-browser for one real browser smoke check after the runtime is reachable If the feature is backend-only or only changes OpenAPI/bootstrap/runtime plumbing without browser-visible effects, targeted backend/runtime evidence is sufficient and agent-browser is optional.
  6. Make the minimum infrastructure/config/code changes needed to unblock the shared path.
  7. Re-run the specific failing command(s), then run the broader shared checks affected by the feature.
  8. Update shared state if the feature proves factual runtime changes workers need (services.yaml, .factory/library/*, mission AGENTS.md if instructed by orchestrator).
  9. In the handoff, be explicit about:
    • which commands were broken before
    • what exact runtime/schema/port behavior is now canonical
    • whether the worker started or reused 8080/5173

Example Handoff

json
{
  "salientSummary": "Aligned local validation to reuse 8080/5173, fixed the PG* projection path for pgschema, and made readiness checks depend on reachable HTTP probes instead of startup logs. `go test ./apps/backend/internal/bootstrap/... -count=1` and the browser smoke path are now green.",
  "whatWasImplemented": "Updated runtime/test infrastructure so the mission uses one canonical local path: backend on 8080, website on 5173, external Postgres on 5432 with a dedicated test schema managed by pgschema. Fixed the failing bootstrap/runtime setup, added explicit readiness gating, and verified the browser lane against the real reused runtime.",
  "whatWasLeftUndone": "",
  "verification": {
    "commandsRun": [
      {
        "command": "go test ./apps/backend/internal/bootstrap/... -count=1",
        "exitCode": 0,
        "observation": "Bootstrap tests passed after env/schema alignment changes."
      },
      {
        "command": "PGHOST=localhost PGPORT=5432 PGDATABASE=opentoggl PGUSER=opentoggl pgschema plan --file apps/backend/internal/platform/schema/schema.sql",
        "exitCode": 0,
        "observation": "Plan executed successfully against the external Postgres service."
      },
      {
        "command": "vp run test:e2e:website -- --list",
        "exitCode": 0,
        "observation": "Website E2E inventory is available against the reused local runtime."
      }
    ],
    "interactiveChecks": [
      {
        "action": "Opened the reused website runtime with agent-browser after HTTP probe success and navigated into the shell.",
        "observed": "The site loaded on 5173 and the shell was interactive without readiness races."
      }
    ]
  },
  "tests": {
    "added": [
      {
        "file": "apps/backend/internal/bootstrap/...",
        "cases": [
          {
            "name": "runtime readiness uses canonical PG* projection",
            "verifies": "pgschema and backend startup follow one aligned env path"
          }
        ]
      }
    ]
  },
  "discoveredIssues": []
}

When to Return to Orchestrator

  • The feature requires changing agreed mission boundaries (different local ports, different database topology, or embedded Postgres)
  • A required external dependency cannot be restored (localhost:5432, localhost:6379, reused 8080/5173 runtime)
  • The canonical runtime path is still ambiguous after investigation

© CorrectRoadH, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .factory/skills/test-platform-worker of CorrectRoadH/OpenTickly.

Open the folder on GitHubat commit 5ffd0a0

Compare with similar skills

Test Platform Worker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Test Platform Worker compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Platform Worker this skillCorrectRoadH/OpenTickly306—~1.2kAutomated safety check: PassAGPL-3.0
Worker Visualizernexu-io/open-design100k—~998Automated safety check: PassApache-2.0
Homelab Network Readinessaffaan-m/ECC274k1 repos~1.9kAutomated safety check: PassMIT
Agent Worker Specialistruvnet/ruflo74k3 repos~1.4kAutomated safety check: PassMIT
Loop Workerruvnet/ruflo74k—~297Automated safety check: PassMIT
Service Workerthedaviddias/Front-End-Checklist74k—~478Automated safety check: PassMIT

Similar skills

  • Worker Visualizer

    nexu-io/open-design

    A real-time data/particle/simulation visualizer whose heavy compute runs in a Web Worker (off the main thread), optionally sharing memory with the UI via SharedArrayBuffer, and renders to a canvas…

    100k GitHub stars~998 tokensUpdated today
    Auto-check passed
  • Readiness checklist for homelab VLAN segmentation, local DNS filtering (Pi-hole, AdGuard Home), and WireGuard-style remote access.

    274k GitHub starsUsed in 1 repo~1.9k tokens
    Backend & APIsAuto-check passed
  • Agent skill for worker-specialist - invoke with $agent-worker-specialist

    74k GitHub starsUsed in 3 repos~1.4k tokens
    Auto-check passed
  • Loop Worker

    ruvnet/ruflo

    Run Ruflo background workers using Claude Code native /loop scheduling

    74k GitHub stars~297 tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Service Worker

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing repeat-visit performance, adding offline support, or evaluating PWA readiness for a web application.

    74k GitHub stars~478 tokensUpdated yesterday
    Auto-check passed
  • Hardens code against vulnerabilities. An agent skill from penpot/penpot.

    61k GitHub starsUsed in 6 repos~4.7k tokens
    SecurityAuto-check: notes

More from CorrectRoadH/OpenTickly

All 10 skills in this repo
  • Backend Test Worker

    CorrectRoadH/OpenTickly

    Build and verify real-Postgres Go tests and thin transport smoke for tracking behavior.

    306 GitHub stars~1.3k tokensUpdated 5 days ago
    Auto-check passed
  • Frontend Test Worker

    CorrectRoadH/OpenTickly

    Build and verify page-flow and E2E coverage for the tracking browser surface.

    306 GitHub stars~1.4k tokensUpdated 5 days ago
    Auto-check passed
  • Fullstack Regression Worker

    CorrectRoadH/OpenTickly

    Build cross-layer regression coverage that ties browser-visible behavior to backend truth.

    306 GitHub stars~1.1k tokensUpdated 5 days ago
    Auto-check passed
  • Tracking Backend Worker

    CorrectRoadH/OpenTickly

    Update backend timer/time-entry contracts, regressions, and source docs for the timer refactor mission.

    306 GitHub stars~1.2k tokensUpdated 5 days ago
    Auto-check passed
  • Tracking Doc Worker

    CorrectRoadH/OpenTickly

    Audit and finalize inline source-document status blocks for the timer refactor mission.

    306 GitHub stars~819 tokensUpdated 5 days ago
    Auto-check passed
  • Tracking Frontend Worker

    CorrectRoadH/OpenTickly

    Refactor and verify website timer/time-entry surfaces on the reused local runtime.

    306 GitHub stars~1.2k tokensUpdated 5 days ago
    Auto-check passed

Questions about Test Platform Worker

What does Test Platform Worker do?

Harden shared test infrastructure, runtime readiness, schema setup, and parallel lane behavior. Test Platform Worker is an agent skill from CorrectRoadH/OpenTickly. Harden shared test infrastructure, runtime readiness, schema setup, and parallel lane behavior.

How do I install Test Platform Worker in Claude Code?

Run `npx skills add CorrectRoadH/OpenTickly --skill test-platform-worker -a claude-code`. Or copy the skill folder (.factory/skills/test-platform-worker in CorrectRoadH/OpenTickly) into .claude/skills/test-platform-worker in your project. Claude Code loads it when a task matches its description.

How do I install Test Platform Worker in Codex?

Run `npx skills add CorrectRoadH/OpenTickly --skill test-platform-worker -a codex`. Or copy the skill folder (.factory/skills/test-platform-worker in CorrectRoadH/OpenTickly) into .agents/skills/test-platform-worker in your project. Codex loads it when a task matches its description.

Can I use Test Platform Worker in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CorrectRoadH/OpenTickly --skill test-platform-worker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-platform-worker, .gemini/skills/test-platform-worker, .github/skills/test-platform-worker and .opencode/skills/test-platform-worker in your project.

What does Test Platform Worker need to run?

SKILL.md names no scripts, command-line tools or credentials: Test Platform Worker is instructions for the agent only.

Does Test Platform Worker access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Test Platform Worker safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Test Platform Worker use?

Test Platform Worker is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Platform Worker use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Test Platform Worker?

Skills that share tags, products or a category with Test Platform Worker: Worker Visualizer (nexu-io/open-design, 100k stars), Homelab Network Readiness (affaan-m/ECC, 274k stars), Agent Worker Specialist (ruvnet/ruflo, 74k stars) and Loop Worker (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Platform Worker?

CorrectRoadH (a GitHub user) maintains it in CorrectRoadH/OpenTickly, which has 306 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 2, 2026.

Source: CorrectRoadH/OpenTickly on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.