Weavebench Cua Reproduce
AMAP-ML/LongHorizon-Harness
Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.
Create a new GitHub issue in this repository — a bug report, an enhancement request, or a followup/sub-issue found while implementing another task.
$ npx skills add epam/cloud-pipeline --skill file-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install epam/cloud-pipeline file-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/file-issue .claude/skills/file-issue && rm -rf skills-srcUse ~/.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/
Install the "file-issue" agent skill from https://github.com/epam/cloud-pipeline/tree/develop/.agents/skills/file-issue into .claude/skills/file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/epam/cloud-pipeline/tree/develop/.agents/skills/file-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add epam/cloud-pipeline --skill file-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install epam/cloud-pipeline file-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/file-issue .agents/skills/file-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "file-issue" agent skill from https://github.com/epam/cloud-pipeline/tree/develop/.agents/skills/file-issue into .agents/skills/file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add epam/cloud-pipeline --skill file-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install epam/cloud-pipeline file-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/file-issue .cursor/skills/file-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "file-issue" agent skill from https://github.com/epam/cloud-pipeline/tree/develop/.agents/skills/file-issue into .cursor/skills/file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/epam/cloud-pipeline.git --path .agents/skills/file-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add epam/cloud-pipeline --skill file-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install epam/cloud-pipeline file-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/file-issue .gemini/skills/file-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "file-issue" agent skill from https://github.com/epam/cloud-pipeline/tree/develop/.agents/skills/file-issue into .gemini/skills/file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install epam/cloud-pipeline file-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add epam/cloud-pipeline --skill file-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/file-issue .github/skills/file-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "file-issue" agent skill from https://github.com/epam/cloud-pipeline/tree/develop/.agents/skills/file-issue into .github/skills/file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add epam/cloud-pipeline --skill file-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install epam/cloud-pipeline file-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/cloud-pipeline.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/file-issue .opencode/skills/file-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "file-issue" agent skill from https://github.com/epam/cloud-pipeline/tree/develop/.agents/skills/file-issue into .opencode/skills/file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "file-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
file-issueCreate a new GitHub issue in this repository — a bug report, an enhancement request, or a followup/sub-issue found while implementing another task.
File Issue is an agent skill from epam/cloud-pipeline. Create a new GitHub issue in this repository — a bug report, an enhancement request, or a followup/sub-issue found while implementing another task. Use when asked to file, open, or write up an issue, not when implementing one that already exists.
Its SKILL.md is about 340 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering QA and bug reports. It works with GitHub. The repository describes itself as: Cloud agnostic genomics analysis, scientific computation and storage platform. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit 5017688. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
ghFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
File Issue loads about 339 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 151 words of instructions outside code blocks.
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.
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.
The full file from epam/cloud-pipeline at commit 5017688, republished under its Apache-2.0 licence (© epam). 151 words, ~339 tokens.
.claude/skills/file-issue/SKILL.md (or your agent's skills folder).Pick the file in .github/ISSUE_TEMPLATE/ whose about: matches what you are filing, and fill in its
sections rather than a shape of your own. Skip a section the issue genuinely has nothing for rather
than leaving the placeholder text in. The title is yours to write.
Labels — gh label list for the current set. Pass the template's kind/*, intel/artificial 🤖
(never intel/natural 🧐, whatever the template carries — CONTRIBUTIONS.md → "Authorship labels"),
and sys/<area> / cloud/<provider> where the issue clearly names one. Leave priority/*, goal/*,
kb, kind/duplicate, kind/wontfix, kind/question and dependencies unset unless told directly
to add them.
A followup or sub-issue found mid-task uses the matching template too, linked to its parent —
CONTRIBUTIONS.md → "Task entity properties" has the convention.
Attended, confirm the title and labels with whoever asked before creating it. Unattended, create one only where the trigger said to file it, and give the issue number and URL in the hand-back.
© epam, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/file-issue of epam/cloud-pipeline.
Open the folder on GitHubat commit 5017688
File Issue 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| File Issue this skillepam/cloud-pipeline | 162 | — | ~339 | Automated safety check: Pass | Apache-2.0 | |
| Weavebench Cua ReproduceAMAP-ML/LongHorizon-Harness | 1.7k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Evidence-Driven Testingmichaelshimeles/skills | 1.3k | 1 repos | ~3.9k | Automated safety check: Pass | None | |
| Create GitHub IssueNVIDIA/OpenShell | 15k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Triage IssuesClickHouse/clickhouse-java | 1.6k | — | ~904 | Automated safety check: Pass | Apache-2.0 | |
| Gentle AI Issue CreationGentleman-Programming/gentle-shell | 1.2k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 |
AMAP-ML/LongHorizon-Harness
Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.
michaelshimeles/skills
Records an annotated screen recording of the agent testing an app hands-on, then posts the video and a results summary to the PR and tracker issue.
NVIDIA/OpenShell
Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.
ClickHouse/clickhouse-java
Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.
Gentleman-Programming/gentle-shell
Create and triage GitHub issues from repository evidence. An agent skill from Gentleman-Programming/gentle-shell.
termio-sh/termio
Diagnose a termio hang, beachball, crash, or 'it froze again' from the evidence macOS and termio actually leave behind — live process samples, crash and CPU-burn reports, the unified log, the…
epam/cloud-pipeline
Open a user-visible client/ change in a browser against a real Cloud Pipeline deployment.
epam/cloud-pipeline
Learn which toolchains and environments this workstation has and how to invoke them, or set them up when they are missing.
epam/cloud-pipeline
Required before you commit, push or open a pull request here, asked or not.
epam/cloud-pipeline
Required before adding or changing anything an agent reads — a convention in AGENTS.md, a procedure as a skill, a pattern-scoped rule.
epam/cloud-pipeline
Plan the work before you edit — its phases, the model and effort each takes, and whether it is worth a plan file with a ledger beside it.
epam/cloud-pipeline
Find and run the checks a change owes, from what it touches and what that can reach.
Works with
Categories
Create a new GitHub issue in this repository — a bug report, an enhancement request, or a followup/sub-issue found while implementing another task. File Issue is an agent skill from epam/cloud-pipeline. Create a new GitHub issue in this repository — a bug report, an enhancement request, or a followup/sub-issue found while implementing another task.
File Issue fits situations like: write up an issue; not when implementing one that already exists.
Run `npx skills add epam/cloud-pipeline --skill file-issue -a claude-code`. Or copy the skill folder (.agents/skills/file-issue in epam/cloud-pipeline) into .claude/skills/file-issue in your project. Claude Code loads it when a task matches its description.
Run `npx skills add epam/cloud-pipeline --skill file-issue -a codex`. Or copy the skill folder (.agents/skills/file-issue in epam/cloud-pipeline) into .agents/skills/file-issue in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add epam/cloud-pipeline --skill file-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/file-issue, .gemini/skills/file-issue, .github/skills/file-issue and .opencode/skills/file-issue in your project.
Going by SKILL.md and its folder, File Issue needs the command-line tools its instructions call (gh).
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
File Issue is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 339 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with File Issue: Weavebench Cua Reproduce (AMAP-ML/LongHorizon-Harness, 1.7k stars), Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars), Create GitHub Issue (NVIDIA/OpenShell, 15k stars) and Triage Issues (ClickHouse/clickhouse-java, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
epam (a GitHub organization) maintains it in epam/cloud-pipeline, which has 162 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 6, 2026.
Source: epam/cloud-pipeline on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.