agentsclimarketplace

Opp repl github actions

Skill tabgab/opp_repl-skill/opp-repl-github-actions

Composable Anthropic-format Agent Skills for driving OMNeT++ simulations via opp_repl. Works in Claude, Windsurf, and any SKILL.md-aware agent.

Install
npx -y skills add tabgab/opp_repl-skill --skill opp-repl-github-actions

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Dispatch GitHub Actions CI workflows from opp_repl. Requires `github` extra, a personal access token at ~/.ssh/github_repo_token (repo + workflow scopes), and github_owner/github_repository/github_workflows parameters in the project's .opp file. dispatch_workflow and dispatch_all_workflows fire workflow_dispatch events; combine with `opp-repl-fingerprint-tests` etc. locally.

SKILL.md

2.7 KB, as published. Nobody here has run it

GitHub Actions integration

Fire workflow_dispatch events on the project's GitHub repository directly from opp_repl. Handy for triggering expensive CI suites (full fingerprint run, cluster tests) without leaving the REPL.

Upstream reference: https://github.com/omnetpp/opp_repl/blob/main/doc/github_actions.md

Prerequisites

  1. pip install "opp_repl[github]" (pulls requests).

  2. Personal access token in ~/.ssh/github_repo_token (file permissions 600) with scopes repo and workflow.

  3. .opp file includes GitHub fields:

    SimulationProject(
        name="inet",
        root_folder=".",
        ...,
        github_owner="inet-framework",
        github_repository="inet",
        github_workflows=[
            "fingerprint-tests.yml",
            "statistical-tests.yml",
            "chart-tests.yml",
        ],
    )
    

Python API

# Dispatch a single workflow
dispatch_workflow("fingerprint-tests.yml")

# Dispatch all configured workflows for the default project
dispatch_all_workflows()

# Target a specific project and branch
dispatch_workflow("fingerprint-tests.yml",
                  simulation_project=inet_project,
                  ref="topic/my-feature")

Returns the HTTP response from GitHub. No CLI wrapper is bundled for this function; use the REPL or an ad-hoc python -c.

Typical workflow

  1. Finish a local change and run smoke tests locally.
  2. dispatch_workflow("fingerprint-tests.yml", ref="my-branch") to kick a longer CI run while you context-switch.
  3. Inspect the results in GitHub Actions UI when ready.

Pitfalls

  • The token file must not be group/world readable. GitHub will 400 / 401 with ambiguous messages otherwise.
  • github_workflows lists YAML file names, not display names. Check .github/workflows/ in the repo.
  • workflow_dispatch must be declared in the workflow YAML itself (on: [workflow_dispatch]), or the API returns 422.
  • dispatch_workflow() just TRIGGERS the run; results live on GitHub. If you need local verdicts, run the equivalent run_*_tests() instead.

See also

  • opp-repl-opp-files — where github_* parameters go.
  • Every opp-repl-*-tests skill — what workflows typically run.

Gives 0 of the 12 instructions most ci cd skills give

Counted across 392 of the 394 authors here whose files we hold, read 2026-08-06

  • pin third-party actions to full commit SHAsin 33 of 392
  • cache dependencies appropriatelyin 24 of 392, across 12 files
  • optimize pipelines exceeding ten minutesin 20 of 392, across 6 files
  • enforce all quality gates before mergein 20 of 392, across 7 files
  • Configure branch protection rulesin 19 of 392, across 5 files
  • use environments for deployment trackingin 19 of 392, across 7 files
  • implement manual gates for productionin 19 of 392, across 7 files
  • implement security scanningin 18 of 392, across 5 files
  • fix failing code instead of disabling checksin 18 of 392, across 4 files
  • use CI/CD variables for secretsin 18 of 392, across 6 files
  • move checks upstream in the pipelinein 17 of 392, across 3 files
  • use specific image tagsin 17 of 392, across 5 files

Said here and by no other author read

  • install the github extra
  • provide a personal access token
  • set file permissions to 600
  • configure github fields in project file
  • verify workflow dispatch is declared
  • run smoke tests locally

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.