Skill Seekers Builder
yusufkaraaslan/Skill_Seekers
Detects the type of a knowledge source and uses the Skill Seekers MCP tools to turn docs, repos, PDFs or videos into packaged AI skills.
Fetches GitHub issues from URLs and creates implementation plans for UUI.
Install Uui GitHub Issue Workflow
$ npx skills add epam/UUI --skill uui-github-issue-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install epam/UUI uui-github-issue-workflow --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/UUI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/github-issue-workflow .claude/skills/uui-github-issue-workflow && 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 "uui-github-issue-workflow" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/github-issue-workflow into .claude/skills/uui-github-issue-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-github-issue-workflow", 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/UUI/tree/develop/.cursor/skills/github-issue-workflowType 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/UUI --skill uui-github-issue-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install epam/UUI uui-github-issue-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/github-issue-workflow .agents/skills/uui-github-issue-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "uui-github-issue-workflow" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/github-issue-workflow into .agents/skills/uui-github-issue-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-github-issue-workflow", 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/UUI --skill uui-github-issue-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install epam/UUI uui-github-issue-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/github-issue-workflow .cursor/skills/uui-github-issue-workflow && 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 "uui-github-issue-workflow" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/github-issue-workflow into .cursor/skills/uui-github-issue-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-github-issue-workflow", 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/UUI.git --path .cursor/skills/github-issue-workflow--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/UUI --skill uui-github-issue-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install epam/UUI uui-github-issue-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/github-issue-workflow .gemini/skills/uui-github-issue-workflow && 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 "uui-github-issue-workflow" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/github-issue-workflow into .gemini/skills/uui-github-issue-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-github-issue-workflow", 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/UUI uui-github-issue-workflowInstalls 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/UUI --skill uui-github-issue-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/github-issue-workflow .github/skills/uui-github-issue-workflow && 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 "uui-github-issue-workflow" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/github-issue-workflow into .github/skills/uui-github-issue-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-github-issue-workflow", 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/UUI --skill uui-github-issue-workflow -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/UUI uui-github-issue-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/github-issue-workflow .opencode/skills/uui-github-issue-workflow && 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 "uui-github-issue-workflow" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/github-issue-workflow into .opencode/skills/uui-github-issue-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-github-issue-workflow", 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.
Facts
- Skill name
uui-github-issue-workflow- GitHub stars
- 248
- Token cost
- ~1.5k tokens
- SKILL.md length
- 614 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Fetches GitHub issues from URLs and creates implementation plans for UUI.
- Works in 2 steps: Analysis (always run first) → Implementation (only after user confirms)
- The user provides a GitHub issue link (github.com/.../issues/N)
- SKILL.md covers Trigger, Phase 1: Analysis (always run…, Phase 2: Implementation (only… and Edge Cases, plus 1 more section
- Reaches github.com
What it does
Uui GitHub Issue Workflow is an agent skill from epam/UUI. Fetches GitHub issues from URLs and creates implementation plans for UUI. Use when the user provides a GitHub issue link (github.com/.../issues/N), asks to plan work from an issue, or implement/fix an issue by URL.
Its SKILL.md is about 1.5k 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 Agent Workflows, covering Planning. It works with GitHub and Model Context Protocol. The repository describes itself as: React-based components and accelerators library built by EPAM Systems. The licence is MIT.
When your agent uses it
- The user provides a GitHub issue link (github.com/.../issues/N)
- Asks to plan work from an issue
- Implement/fix an issue by URL
Example prompts
- “Use the uui-github-issue-workflow skill to fetch GitHub issues from URLs and creates implementation plans for UUI”
- “/uui-github-issue-workflow”
Workflow steps
2 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit fd11393. 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 markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
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
Uui GitHub Issue Workflow loads about 1.5k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 614 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.
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 epam/UUI at commit fd11393, republished under its MIT licence (© epam). 614 words, ~1,537 tokens.
Download SKILL.mdSave it as
.claude/skills/uui-github-issue-workflow/SKILL.md (or your agent's skills folder).- name
- uui-github-issue-workflow
- description
- Fetches GitHub issues from URLs and creates implementation plans for UUI. Use when the user provides a GitHub issue link (github.com/.../issues/N), asks to plan work from an issue, or implement/fix an issue by URL.
GitHub Issue Workflow
When the user provides a GitHub issue URL or asks to plan work from an issue, follow this two-phase workflow. Always run Phase 1 first; only proceed to Phase 2 after the user confirms.
Trigger
Apply this skill when the user:
- Pastes a GitHub issue URL (e.g.
https://github.com/epam/UUI/issues/123) - Asks to "plan", "implement", or "fix" an issue by link
- References an issue with a
github.com/.../issues/Nor.../pull/NURL
Phase 1: Analysis (always run first)
Run Phase 1 to analyze scope before implementation. Do not implement yet. Limit exploration; produce a short analysis and stop.
1. Parse the URL
Extract from the URL:
- owner — e.g.
epamfromgithub.com/epam/UUI/issues/123 - repo — e.g.
UUI - issue_number — e.g.
123
Supported patterns:
https://github.com/{owner}/{repo}/issues/{number}https://github.com/{owner}/{repo}/pull/{number}(PRs are issues; useissue_numberfrom URL)
If the URL is invalid or cannot be parsed, ask the user to provide a valid github.com/.../issues/N URL.
2. Fetch Issue Content (Dual Path)
Always try GitHub MCP first. Only fall back to WebFetch if MCP is unavailable.
Step 1: Check for GitHub MCP server
Browse the MCP tool descriptors folder to find a GitHub MCP server. Look for server folders that contain GitHub-related tools (e.g. get_issue, issue_read, get-issue). Common server names: github, github-mcp, github-mcp-server.
If a GitHub MCP server is found, read its tool descriptor to get the exact tool name and parameters, then call it:
CallMcpTool
server: <discovered GitHub MCP server name>
toolName: <issue read tool from descriptor>
arguments: { owner, repo, issue_number }- MCP returns structured JSON with title, body, labels, state, etc.
- If the call succeeds, use the response directly.
Step 2: Fall back to WebFetch (only if MCP is not available or fails)
If no GitHub MCP server is configured, or the MCP call fails:
- Use
WebFetchwith the full issue URL - Parse the returned content (markdown/HTML) to extract:
- Issue title (from page heading or title element)
- Issue description/body
- Labels or type indicators if visible
3. Produce Short Analysis (Phase 1 only)
Based on the issue content, produce a concise analysis:
| Section | Content |
|---|---|
| Summary | Title, type (bug/feature/refactor/docs), 2–4 key points from description |
| Affected Areas | Package(s), likely files or components (high-level; no deep codebase exploration yet) |
| Complexity Estimate | small / medium / large — based on description scope |
| Proposed Approach | 1–2 sentences on how to fix or implement |
Show full SKILL.md (258 more words)Show less
4. Stop and Ask for Confirmation
Do not create a full implementation plan or make any code changes.
Present the analysis and ask:
"Here's my analysis. Proceed with full implementation? Any changes to scope or approach?"
Wait for the user to confirm or request changes. Only after explicit confirmation (e.g. "yes", "proceed", "go ahead") move to Phase 2.
Phase 2: Implementation (only after user confirms)
Run Phase 2 only when the user has approved the analysis or provided adjustments.
1. Create Full Implementation Plan
Produce a structured plan with these sections:
| Section | Content |
|---|---|
| Issue Summary | Title, type (bug/feature/refactor/docs), key points from description |
| Branch Name | Follow pr-contributing: fix/123-description for bugs, feature/456-description for features. Use kebab-case for the description part. |
| Affected Areas | Package(s) (e.g. uui, uui-components), likely files, components |
| Implementation Steps | Ordered tasks. For component work, follow components patterns (wrapping vs new, withMods, file paths). |
| Testing | Unit tests (unit-testing), E2E/screenshot tests if UI changes (e2e-testing) |
| Documentation | If API changes: examples, Property Explorer (documentation) |
| Pre-PR Checklist | From pr-contributing: tests, lint, bundle size, changelog |
2. Output Format (Phase 2)
Use this template:
## Implementation Plan: #[issue_number] [Title]
### Summary
- **Type:** [bug|feature|refactor|docs]
- **Key points:** [bullet points from description]
### Branch
`fix/123-description` / `feature/456-description`
### Affected Areas
- Package: ...
- Files: ...
### Steps
1. ...
2. ...
### Testing
- Unit: ...
- E2E: (if UI changes)
### Documentation
- (if API changes)
### Checklist
- [ ] yarn test
- [ ] yarn test-update (if UI)
- [ ] yarn test-e2e (if UI)
- [ ] yarn eslint, yarn stylelint
- [ ] yarn track-bundle-size
- [ ] changelog.md3. Execute Implementation
After presenting the plan, proceed with implementation steps as approved by the user.
Edge Cases
| Case | Action |
|---|---|
| Invalid URL | Ask for a valid github.com/.../issues/N URL |
PR URL (/pull/N)** | Extract issue_number from URL; MCP issue_read works for PRs in many setups. Otherwise use web fetch. |
| MCP call fails | Proceed immediately with web fetch (WebFetch tool); do not retry MCP. |
References
- Branch naming, checklist: pr-contributing
- Component patterns: components
- Doc examples, Property Explorer: documentation
- Unit tests: unit-testing
- E2E/screenshot tests: e2e-testing
© epam, MIT. 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 .cursor/skills/github-issue-workflow of epam/UUI.
Open the folder on GitHubat commit fd11393
Compare with similar skills
Uui GitHub Issue Workflow 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 |
|---|---|---|---|---|---|---|
| Uui GitHub Issue Workflow this skillepam/UUI | 248 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Skill Seekers Builderyusufkaraaslan/Skill_Seekers | 15k | — | ~760 | Automated safety check: Pass | MIT | |
| Codex with ChatGPT Planning LoopXiaoDuoYa/codex-with-chatgpt | 7.1k | — | ~11k | Automated safety check: Notes | MIT | |
| Helmor CLIdohooo/helmor | 1.3k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Spec Driven Developzhu1090093659/deepseek-pp | 1.9k | — | ~6.9k | Automated safety check: Pass | Apache-2.0 | |
| Ask NavigatorYeachan-Heo/oh-my-claudecode | 40k | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
Codex with ChatGPT Planning Loop
XiaoDuoYa/codex-with-chatgpt
Uses ChatGPT in the browser as the planning and review brain for a Codex session, with Codex keeping all execution and ChatGPT reading the workspace through a bridge.
Helmor CLI
dohooo/helmor
Use the Helmor CLI to remote-control Helmor from the terminal.
Spec Driven Develop
zhu1090093659/deepseek-pp
Automates pre-development workflow for large-scale complex tasks.
Ask Navigator
Yeachan-Heo/oh-my-claudecode
Charts a foggy effort into a map of decision tickets on the repo's issue tracker and works through them one per session, producing decisions rather than deliverables.
- Official
MCP Apps Builder
awslabs/cli-agent-orchestrator
Load the official MCP Apps builder skills (create-mcp-app, migrate-oai-app, add-app-to-server, convert-web-app) from github.com/modelcontextprotocol/ext-apps.
More from epam/UUI
All 10 skills in this repoUui Components
epam/UUI
Helps create and modify UUI (EPAM Unified UI) components following established patterns.
Uui Data Sources
epam/UUI
Helps work with UUI DataSources (ArrayDataSource, LazyDataSource, AsyncDataSource) powering PickerInput, DataTable, FiltersPanel, and other data-driven components.
Uui Documentation
epam/UUI
Helps update UUI documentation, add doc examples, configure Property Explorer, and manage component API documentation.
Uui E2E Testing
epam/UUI
Helps create and maintain E2E and screenshot tests for UUI components using Playwright.
Uui PR Contributing
epam/UUI
Guides the UUI pull request process including branch naming, pre-PR checklist, changelog updates, and quality requirements.
Uui Services Context
epam/UUI
Helps work with UUI services layer including ContextProvider, ApiContext, ModalContext, NotificationContext, and useUuiContext.
Related
Works with
Categories
Questions about Uui GitHub Issue Workflow
What does Uui GitHub Issue Workflow do?
Fetches GitHub issues from URLs and creates implementation plans for UUI. Uui GitHub Issue Workflow is an agent skill from epam/UUI. Fetches GitHub issues from URLs and creates implementation plans for UUI.
When should I use Uui GitHub Issue Workflow?
Uui GitHub Issue Workflow fits situations like: the user provides a GitHub issue link (github.com/.../issues/N); asks to plan work from an issue; implement/fix an issue by URL.
How do I install Uui GitHub Issue Workflow in Claude Code?
Run `npx skills add epam/UUI --skill uui-github-issue-workflow -a claude-code`. Or copy the skill folder (.cursor/skills/github-issue-workflow in epam/UUI) into .claude/skills/uui-github-issue-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Uui GitHub Issue Workflow in Codex?
Run `npx skills add epam/UUI --skill uui-github-issue-workflow -a codex`. Or copy the skill folder (.cursor/skills/github-issue-workflow in epam/UUI) into .agents/skills/uui-github-issue-workflow in your project. Codex loads it when a task matches its description.
Can I use Uui GitHub Issue Workflow 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 epam/UUI --skill uui-github-issue-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/uui-github-issue-workflow, .gemini/skills/uui-github-issue-workflow, .github/skills/uui-github-issue-workflow and .opencode/skills/uui-github-issue-workflow in your project.
What does Uui GitHub Issue Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Uui GitHub Issue Workflow is instructions for the agent only.
Does Uui GitHub Issue Workflow access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Uui GitHub Issue Workflow 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 Uui GitHub Issue Workflow use?
Uui GitHub Issue Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Uui GitHub Issue Workflow use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Uui GitHub Issue Workflow?
Skills that share tags, products or a category with Uui GitHub Issue Workflow: Skill Seekers Builder (yusufkaraaslan/Skill_Seekers, 15k stars), Codex with ChatGPT Planning Loop (XiaoDuoYa/codex-with-chatgpt, 7.1k stars), Helmor CLI (dohooo/helmor, 1.3k stars) and Spec Driven Develop (zhu1090093659/deepseek-pp, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Uui GitHub Issue Workflow?
epam (a GitHub organization) maintains it in epam/UUI, which has 248 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 29, 2026.
Source: epam/UUI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.