Lead-to-Payment Sales Flow
hewi333/Mom-n-Pop-Skills
Runs a small service business lead from intake through estimate, owner approval over Telegram, Stripe payment link and customer email draft to payment tracking.
Prioritize GitHub issues by ROI, solution sanity, and architectural impact.
$ npx skills add LeoYeAI/openclaw-master-skills --skill issue-prioritizer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills issue-prioritizer --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/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/issue-prioritizer .claude/skills/issue-prioritizer && 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 "issue-prioritizer" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/issue-prioritizer into .claude/skills/issue-prioritizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-prioritizer", 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/LeoYeAI/openclaw-master-skills/tree/main/skills/issue-prioritizerType 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 LeoYeAI/openclaw-master-skills --skill issue-prioritizer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills issue-prioritizer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/issue-prioritizer .agents/skills/issue-prioritizer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-prioritizer" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/issue-prioritizer into .agents/skills/issue-prioritizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-prioritizer", 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 LeoYeAI/openclaw-master-skills --skill issue-prioritizer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills issue-prioritizer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/issue-prioritizer .cursor/skills/issue-prioritizer && 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 "issue-prioritizer" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/issue-prioritizer into .cursor/skills/issue-prioritizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-prioritizer", 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/LeoYeAI/openclaw-master-skills.git --path skills/issue-prioritizer--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 LeoYeAI/openclaw-master-skills --skill issue-prioritizer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills issue-prioritizer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/issue-prioritizer .gemini/skills/issue-prioritizer && 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 "issue-prioritizer" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/issue-prioritizer into .gemini/skills/issue-prioritizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-prioritizer", 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 LeoYeAI/openclaw-master-skills issue-prioritizerInstalls 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 LeoYeAI/openclaw-master-skills --skill issue-prioritizer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/issue-prioritizer .github/skills/issue-prioritizer && 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 "issue-prioritizer" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/issue-prioritizer into .github/skills/issue-prioritizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-prioritizer", 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 LeoYeAI/openclaw-master-skills --skill issue-prioritizer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills issue-prioritizer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/issue-prioritizer .opencode/skills/issue-prioritizer && 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 "issue-prioritizer" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/issue-prioritizer into .opencode/skills/issue-prioritizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-prioritizer", 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.
issue-prioritizerPrioritize GitHub issues by ROI, solution sanity, and architectural impact.
Issue Prioritizer is an agent skill from LeoYeAI/openclaw-master-skills. Prioritize GitHub issues by ROI, solution sanity, and architectural impact. Use when triaging or ranking issues to identify quick wins, over-engineered proposals, and actionable bugs. Don't use when managing forks (use fork-manager) or general GitHub queries (use github). Read-only — never modifies repositories.
Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files (for example `README.md`, `_meta.json` and `commands/CLAUDE.md`).
It sits in Sales & Support, covering Proposals and quotes. It works with GitHub and Telegram. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. 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.
Hosts in commands or code, which the agent is likely to contact:
github.comFrom 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.
Issue Prioritizer loads about 3.9k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 1,142 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 LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,142 words, ~3,944 tokens.
.claude/skills/issue-prioritizer/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.Analyze issues from a GitHub repository and rank them by Adjusted Score — ROI penalized by Tripping Scale (solution sanity), Architectural Impact, and Actionability.
This is a read-only skill. It analyzes and presents information. The user makes all decisions.
fork-manager insteadgithub insteadpr-review insteadgh CLI authenticated (gh auth login)If the user didn't specify a repository, ask which one to analyze (format: owner/repo).
Basic fetch (most recent):
gh issue list --repo {owner/repo} --state open --limit {limit} --json number,title,body,labels,createdAt,comments,urlDefault limit is 30. Store the full JSON response.
Targeted fetch with --topic:
When the user specifies --topic <keyword> (e.g. --topic telegram, --topic agents), use GitHub search to find issues matching that topic instead of just fetching the most recent:
# Search by topic keywords in title and body
gh issue list --repo {owner/repo} --state open --limit {limit} --search "{topic} in:title,body" --json number,title,body,labels,createdAt,comments,urlMultiple topics can be combined: --topic "telegram agents" searches for issues containing either term.
Targeted fetch with --search:
When the user specifies --search <query>, pass it directly as a GitHub search query for full control:
gh issue list --repo {owner/repo} --state open --limit {limit} --search "{query}" --json number,title,body,labels,createdAt,comments,urlExamples:
--search "telegram in:title" — only title matches--search "label:bug telegram" — bugs mentioning telegram--search "label:bug,enhancement telegram agents" — bugs or enhancements about telegram/agents--search "comments:>5 telegram" — active discussions about telegramLabel-based fetch with --label:
gh issue list --repo {owner/repo} --state open --limit {limit} --label "{label}" --json number,title,body,labels,createdAt,comments,urlAll fetch modes can be combined: --topic telegram --label bug --limit 50 fetches up to 50 open bugs about telegram.
Error handling:
gh auth login--limitowner/repoNote: If user specified --include-with-prs, skip this entire step and proceed to Step 4 with all fetched issues.
Before analyzing, check for open PRs that already address issues to avoid duplicate work.
gh pr list --repo {owner/repo} --state open --json number,title,body,urlDetect linked issues using ALL of these methods:
Method 1 — Explicit Keywords (high confidence): Scan PR title and body (case-insensitive):
fixes #N, fix #N, fixed #Ncloses #N, close #N, closed #Nresolves #N, resolve #N, resolved #NMethod 2 — Issue References (medium confidence):
#N anywhere in textissue N, issue #N, related to #N, addresses #NMethod 3 — Title Similarity (fuzzy): Normalize titles (lowercase, remove punctuation/common words). If 70%+ word overlap → likely linked.
Method 4 — Semantic Matching (ambiguous cases): Extract key terms from issue (error names, function names, components). Check if PR body discusses same things.
Confidence icons:
Remove linked issues from analysis. Report them separately before the main report.
If all issues have PRs, report that and exit.
For each remaining issue, score the following:
Base score: 5. Adjustments:
| Signal | Adjustment |
|---|---|
| Documentation only | -3 |
| Has proposed solution | -2 |
| Has reproduction steps | -1 |
| Clear error message | -1 |
| Unknown root cause | +3 |
| Architectural change | +3 |
| Race condition/concurrency | +2 |
| Security implications | +2 |
| Multiple systems involved | +2 |
| Range | Level | Examples |
|---|---|---|
| 8-10 | Critical | Crash, data loss, security vulnerability, service down |
| 6-7 | High | Broken functionality, errors, performance issues |
| 4-5 | Medium | Enhancements, feature requests, improvements |
| 1-3 | Low | Cosmetic, documentation, typos |
| Score | Label | Description |
|---|---|---|
| 1 | Total Sanity | Proven approach, standard patterns |
| 2 | Grounded w/Flair | Practical with creative touches |
| 3 | Dipping Toes | Exploring cautiously |
| 4 | Wild Adventure | Bold, risky, unconventional |
| 5 | Tripping | Questionable viability |
Red Flags (+score): rewrite from scratch, buzzwords (blockchain, AI-powered, ML-based), experimental/unstable, breaking change, custom protocol Green Flags (-score): standard approach, minimal change, backward compatible, existing library, well-documented
Always ask: "Is there a simpler way?" before scoring.
| Score | Label | Description |
|---|---|---|
| 1 | Surgical | Isolated fix, 1-2 files, no new abstractions |
| 2 | Localized | Small addition, follows existing patterns exactly |
| 3 | Moderate | New component within existing architecture |
| 4 | Significant | New subsystem, new patterns, affects multiple modules |
| 5 | Transformational | Restructures core, changes paradigms, migration needed |
Red Flags (+score): "rewrite", "refactor entire", new framework for existing capability, changes across >5 files, breaking API changes, scope creep Green Flags (-score): single file fix, uses existing utilities, follows established patterns, backward compatible, easily revertible
Critical: If a simple solution exists, architectural changes are wrong. Don't create a "validation framework" when a single if-check suffices.
| Score | Label | Description |
|---|---|---|
| 1 | Not Actionable | Question, discussion, duplicate, support request |
| 2 | Needs Triage | Missing info, unclear scope, needs clarification |
| 3 | Needs Investigation | Root cause unknown, requires debugging first |
| 4 | Ready to Work | Clear scope, may need some design decisions |
| 5 | PR Ready | Solution is clear, just needs implementation |
Blockers (-score): questions ("how do I?"), discussions ("thoughts?"), labels (duplicate, wontfix, question), missing repro Ready signals (+score): action titles ("fix:", "add:"), proposed solution, repro steps, good-first-issue label, specific files mentioned
issueType: "bug" | "feature" | "docs" | "other"
suggestedLevel:
- "beginner": difficulty 1-3, no security/architecture changes
- "intermediate": difficulty 4-6
- "advanced": difficulty 7+ OR security implications OR architectural changesROI = Importance / Difficulty
AdjustedScore = ROI × TripMultiplier × ArchMultiplier × ActionMultiplierTripping Scale Multiplier:
| Score | Label | Multiplier |
|---|---|---|
| 1 | Total Sanity | 1.00 (no penalty) |
| 2 | Grounded w/Flair | 0.85 |
| 3 | Dipping Toes | 0.70 |
| 4 | Wild Adventure | 0.55 |
| 5 | Tripping | 0.40 |
Architectural Impact Multiplier:
| Score | Label | Multiplier |
|---|---|---|
| 1 | Surgical | 1.00 (no penalty) |
| 2 | Localized | 0.90 |
| 3 | Moderate | 0.75 |
| 4 | Significant | 0.50 |
| 5 | Transformational | 0.25 |
Actionability Multiplier:
| Score | Label | Multiplier |
|---|---|---|
| 5 | PR Ready | 1.00 (no penalty) |
| 4 | Ready to Work | 0.90 |
| 3 | Needs Investigation | 0.70 |
| 2 | Needs Triage | 0.40 |
| 1 | Not Actionable | 0.10 |
Sort all issues by AdjustedScore descending.
═══════════════════════════════════════════════════════════════
ISSUE PRIORITIZATION REPORT
Repository: {owner/repo}
Filter: {topic/search/label or "latest"}
Analyzed: {count} issues
Excluded: {excluded} issues with existing PRs
═══════════════════════════════════════════════════════════════
Quick Wins: {n} | Critical Bugs: {n} | Tripping: {n} | Over-Engineered: {n} | Not Actionable: {n}
═══════════════════════════════════════════════════════════════
TOP 10 BY ADJUSTED SCORE
═══════════════════════════════════════════════════════════════
#123 [Adj: 3.50] ⭐ Quick Win
Fix typo in README
├─ Difficulty: 1/10 | Importance: 4/10 | ROI: 4.00
├─ Trip: ✅ Total Sanity (1/5) | Arch: ✅ Surgical (1/5)
├─ Act: ✅ PR Ready (5/5) | Level: beginner
└─ https://github.com/owner/repo/issues/123
═══════════════════════════════════════════════════════════════
QUICK WINS (High Impact, Low Effort, Sane & Actionable)
═══════════════════════════════════════════════════════════════
#123: Fix typo in README [Adj: 3.50]
Difficulty: 1 | Importance: 4 | beginner
═══════════════════════════════════════════════════════════════
RECOMMENDATIONS BY LEVEL
═══════════════════════════════════════════════════════════════
BEGINNER (Difficulty 1-3, no security/architecture):
- #123: Fix typo - Low risk, good first contribution
INTERMEDIATE (Difficulty 4-6):
- #456: Add validation - Medium complexity, clear scope
ADVANCED (Difficulty 7-10 or security/architecture):
- #789: Refactor auth - Architectural knowledge needed
═══════════════════════════════════════════════════════════════
CRITICAL BUGS (Importance ≥ 8)
═══════════════════════════════════════════════════════════════
#111 [Adj: 1.67] 🔴 Critical
App crashes on startup with large datasets
├─ Difficulty: 6/10 | Importance: 9/10 | ROI: 1.50
├─ Trip: ✅ (2/5) | Arch: ✅ (2/5) | Act: ⚠️ (3/5)
└─ https://github.com/owner/repo/issues/111
═══════════════════════════════════════════════════════════════
TRIPPING ISSUES (Trip ≥ 4 — Review Carefully)
═══════════════════════════════════════════════════════════════
#999 [Trip: 🚨 5/5 — Tripping]
Rewrite entire backend in Rust with blockchain storage
├─ Red Flags: "rewrite from scratch", "blockchain"
├─ Adjusted Score: 0.12 (heavily penalized)
└─ Consider: Is this complexity really needed?
═══════════════════════════════════════════════════════════════
OVER-ENGINEERED (Arch ≥ 4 — Simpler Solution Likely Exists)
═══════════════════════════════════════════════════════════════
#777 [Arch: 🏗️ 5/5 — Transformational]
Add form validation
├─ Proposed: New validation framework with schema definitions
├─ Simpler Alternative: Single validation function, 20 lines
└─ Ask: Why create a framework for one form?
💡 TIP: Maintainers often reject PRs that change architecture
unnecessarily. Always start with the simplest fix.
═══════════════════════════════════════════════════════════════
NOT ACTIONABLE (Actionability ≤ 2)
═══════════════════════════════════════════════════════════════
- #222: "How do I deploy to Kubernetes?" (Act: 1/5 — question)
- #333: Duplicate of #111 (Act: 1/5 — duplicate)
═══════════════════════════════════════════════════════════════
EXCLUDED — EXISTING PRs
═══════════════════════════════════════════════════════════════
#123: Login crashes on empty password
└─ 🔗 PR #456: "Fix login validation" (explicit: fixes #123)
Detection: 🔗 Explicit link | 📎 Referenced | 🔍 Similar title | 💡 Semantic match
═══════════════════════════════════════════════════════════════
SCALE LEGEND
═══════════════════════════════════════════════════════════════
Trip (Solution Sanity): Arch (Structural Impact):
✅ 1-2 = Sane ✅ 1-2 = Minimal change
⚠️ 3 = Cautious ⚠️ 3 = Moderate
🚨 4-5 = Risky 🏗️ 4-5 = Over-engineered
Actionability:
✅ 4-5 = Ready for PR
⚠️ 3 = Needs Investigation
❌ 1-2 = Not Actionable
AdjustedScore = ROI × TripMult × ArchMult × ActionMult
Higher = Better (prioritize first)
🎯 SIMPLICITY PRINCIPLE: If a 10-line fix exists,
a 200-line refactor is wrong.
Mode: SKILL (read-only) — analyzes only, never modifies.
═══════════════════════════════════════════════════════════════--json: Raw JSON output--markdown / --md: Markdown table output--quick-wins: Show only quick wins--level beginner|intermediate|advanced: Filter by contributor level--limit N: Number of issues to analyze (default: 30)--topic <keywords>: Search issues by topic (e.g. --topic telegram, --topic "agents telegram")--search <query>: Raw GitHub search query for full control (e.g. --search "label:bug telegram in:title")--label <name>: Filter by GitHub label (e.g. --label bug)--include-with-prs: Skip PR filtering, include all issuesFor higher-quality scoring, use an LLM to analyze each issue individually. For each issue, prompt the model with the issue details and scoring criteria, requesting structured JSON output:
{
"number": 123,
"difficulty": 5,
"difficultyReasoning": "base 5; has repro (-1); unknown cause (+3) = 7",
"importance": 7,
"importanceReasoning": "broken functionality affecting users",
"tripScore": 2,
"tripLabel": "Grounded with Flair",
"tripRedFlags": [],
"tripGreenFlags": ["minimal change", "standard approach"],
"archScore": 2,
"archLabel": "Localized",
"archRedFlags": [],
"archGreenFlags": ["uses existing patterns"],
"archSimplerAlternative": null,
"actionScore": 4,
"actionLabel": "Ready to Work",
"actionBlockers": [],
"actionReadySignals": ["has proposed solution"],
"issueType": "bug",
"suggestedLevel": "intermediate",
"roi": 1.40,
"adjustedScore": 0.96
}Truncate issue bodies longer than 2000 characters before sending to the model.
When to use LLM Deep Analysis:
Tradeoffs: Slower (~2-5s per issue) but more accurate. 1 API call per issue.
Integration: For each issue, call the LLM with the analysis prompt, parse the JSON response, and merge into results before Step 5 (Categorize).
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 5 other files in skills/issue-prioritizer of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Issue Prioritizer 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 |
|---|---|---|---|---|---|---|
| Issue Prioritizer this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~3.9k | Automated safety check: Pass | MIT | |
| Lead-to-Payment Sales Flowhewi333/Mom-n-Pop-Skills | 122 | — | ~2.8k | Automated safety check: Notes | MIT | |
| Review Proposalsjpicklyk/task-orchestrator | 207 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Supporthaacked/dotfiles | 134 | — | ~2.9k | Automated safety check: Pass | None | |
| B2b Sdr AgentiPythoning/b2b-sdr-agent-template | 190 | — | ~744 | Automated safety check: Pass | MIT-0 | |
| Exploration Modefjrevoredo/mini-diarium | 309 | — | ~3.4k | Automated safety check: Pass | MIT |
hewi333/Mom-n-Pop-Skills
Runs a small service business lead from intake through estimate, owner approval over Telegram, Stripe payment link and customer email draft to payment tracking.
jpicklyk/task-orchestrator
Triages pending improvement-proposal MCP items — presents each with its scope and evidence, collects an accept/reject/defer decision per proposal, and carries out the disposition: project-scoped…
haacked/dotfiles
Support hero workflow — start a ticket investigation with auto-organized notes, find existing notes, or generate the weekly highlights log.
iPythoning/b2b-sdr-agent-template
Open-source B2B AI SDR template. An agent skill from iPythoning/b2b-sdr-agent-template.
fjrevoredo/mini-diarium
Enter exploration mode: a thinking partner for researching and thinking through ideas and problems before implementation.
CraftOS-dev/CraftBot
Context retrieval layer for AI agents across users' applications.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Categories
Prioritize GitHub issues by ROI, solution sanity, and architectural impact. Issue Prioritizer is an agent skill from LeoYeAI/openclaw-master-skills. Prioritize GitHub issues by ROI, solution sanity, and architectural impact.
Issue Prioritizer fits situations like: ranking issues to identify quick wins; over-engineered proposals; actionable bugs; managing forks (use fork-manager).
Run `npx skills add LeoYeAI/openclaw-master-skills --skill issue-prioritizer -a claude-code`. Or copy the skill folder (skills/issue-prioritizer in LeoYeAI/openclaw-master-skills) into .claude/skills/issue-prioritizer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill issue-prioritizer -a codex`. Or copy the skill folder (skills/issue-prioritizer in LeoYeAI/openclaw-master-skills) into .agents/skills/issue-prioritizer 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 LeoYeAI/openclaw-master-skills --skill issue-prioritizer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-prioritizer, .gemini/skills/issue-prioritizer, .github/skills/issue-prioritizer and .opencode/skills/issue-prioritizer in your project.
Going by SKILL.md and its folder, Issue Prioritizer needs the command-line tools its instructions call (gh).
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.
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.
Issue Prioritizer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.9k tokens (SKILL.md is roughly 16k 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 Issue Prioritizer: Lead-to-Payment Sales Flow (hewi333/Mom-n-Pop-Skills, 122 stars), Review Proposals (jpicklyk/task-orchestrator, 207 stars), Support (haacked/dotfiles, 134 stars) and B2b Sdr Agent (iPythoning/b2b-sdr-agent-template, 190 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.