Startup It Troubleshooting
sickn33/agentic-awesome-skills
Practical IT troubleshooting playbooks for small teams without dedicated IT staff.
“Maven 构建故障排查专家，擅长解决依赖冲突、编译错误、插件配置问题”
No licenceAuto-check passed
Install Maven Troubleshoot
$ npx skills add Leavesfly/Jimi --skill maven-troubleshoot -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Leavesfly/Jimi maven-troubleshoot --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/Leavesfly/Jimi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot .claude/skills/maven-troubleshoot && 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 "maven-troubleshoot" agent skill from https://github.com/Leavesfly/Jimi/tree/main/src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot into .claude/skills/maven-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maven-troubleshoot", 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/Leavesfly/Jimi/tree/main/src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshootType 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 Leavesfly/Jimi --skill maven-troubleshoot -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Leavesfly/Jimi maven-troubleshoot --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Leavesfly/Jimi.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot .agents/skills/maven-troubleshoot && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "maven-troubleshoot" agent skill from https://github.com/Leavesfly/Jimi/tree/main/src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot into .agents/skills/maven-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maven-troubleshoot", 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 Leavesfly/Jimi --skill maven-troubleshoot -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Leavesfly/Jimi maven-troubleshoot --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Leavesfly/Jimi.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot .cursor/skills/maven-troubleshoot && 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 "maven-troubleshoot" agent skill from https://github.com/Leavesfly/Jimi/tree/main/src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot into .cursor/skills/maven-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maven-troubleshoot", 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/Leavesfly/Jimi.git --path src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot--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 Leavesfly/Jimi --skill maven-troubleshoot -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Leavesfly/Jimi maven-troubleshoot --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Leavesfly/Jimi.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot .gemini/skills/maven-troubleshoot && 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 "maven-troubleshoot" agent skill from https://github.com/Leavesfly/Jimi/tree/main/src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot into .gemini/skills/maven-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maven-troubleshoot", 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 Leavesfly/Jimi maven-troubleshootInstalls 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 Leavesfly/Jimi --skill maven-troubleshoot -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Leavesfly/Jimi.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot .github/skills/maven-troubleshoot && 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 "maven-troubleshoot" agent skill from https://github.com/Leavesfly/Jimi/tree/main/src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot into .github/skills/maven-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maven-troubleshoot", 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 Leavesfly/Jimi --skill maven-troubleshoot -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Leavesfly/Jimi maven-troubleshoot --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Leavesfly/Jimi.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot .opencode/skills/maven-troubleshoot && 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 "maven-troubleshoot" agent skill from https://github.com/Leavesfly/Jimi/tree/main/src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot into .opencode/skills/maven-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maven-troubleshoot", 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
maven-troubleshoot- GitHub stars
- 237
- Token cost
- ~259 tokens
- SKILL.md length
- 73 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- None found
At a glance
- Works in 4 steps: 收集信息：查看 mvn -X 详细日志、pom.xml… → 定位问题：根据错误信息分类（编译/依赖/插件/网络） → 诊断根因：使用 mvn dependency:tree、mvn… → …
- SKILL.md covers 核心能力, 排查流程 and 常见问题速查
- Calls mvn
About this skill
Maven Troubleshoot is a skill in Leavesfly/Jimi (237 stars). Its SKILL.md is about 259 tokens. No licence found.
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- 收集信息：查看 mvn -X 详细日志、pom.xml 配置、~/.m2/settings.xml
- 定位问题：根据错误信息分类（编译/依赖/插件/网络）
- 诊断根因：使用 mvn dependency:tree、mvn help:effective-pom 等工具
- 给出修复方案：提供具体的 pom.xml 修改建议或命令行参数
What it can do on your machine
Read from SKILL.md and the folder at commit 75e1158. 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
Shell commands in SKILL.md call:
mvn
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
Maven Troubleshoot loads about 259 tokens when it runs. Until then it costs about 14 tokens; SKILL.md has 73 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 73 words (~259 tokens).
- name
- maven-troubleshoot
- version
- 1.0.0
- category
- build
- triggers
- maven, mvn, build, 编译, 依赖冲突
Files
Just SKILL.md in src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot of Leavesfly/Jimi.
Open the folder on GitHubat commit 75e1158
Compare with similar skills
Maven Troubleshoot 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 |
|---|---|---|---|---|---|---|
| Maven Troubleshoot this skillLeavesfly/Jimi | 237 | — | ~259 | Automated safety check: Pass | None | |
| Startup It Troubleshootingsickn33/agentic-awesome-skills | 47k | 2 repos | ~3.6k | Automated safety check: Notes | MIT | |
| Troubleshootingcartography-cncf/cartography | 4.1k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Power Bi Performance Troubleshootinggithub/awesome-copilot | 40k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| WxJava Troubleshooterbinarywang/WxJava | 33k | — | ~135 | Automated safety check: Pass | Apache-2.0 | |
| Mavenskjolber/3d-bin-container-packing | 569 | — | ~886 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Troubleshooting
cartography-cncf/cartography
Diagnose and fix common Cartography intel-module errors — ModuleNotFoundError, PropertyRef validation failed, GraphJob failed, missing relationships, MatchLink misses, cleanup deleting too much…
- Official
Power Bi Performance Troubleshooting
github/awesome-copilot
Systematic Power BI performance troubleshooting prompt for identifying, diagnosing, and resolving performance issues in Power BI models, reports, and queries.
WxJava Troubleshooter
binarywang/WxJava
排查 WxJava 在配置初始化、access token、签名验签、支付证书、回调通知、序列化、网络请求和多账号隔离方面的问题。适用于用户提供异常、日志、请求响应或“WxJava 为什么不能调用”的场景。
Maven
skjolber/3d-bin-container-packing
Maven build expertise for this multi-module Java project. An agent skill from skjolber/3d-bin-container-packing.
- Official
Bigquery Troubleshooting
google/skills
Provides diagnostic workflows and step-by-step root-cause analysis procedures for actively broken, failing, or slow BigQuery jobs, execution graph and query plan stage bottlenecks, system…
More from Leavesfly/Jimi
All 9 skills in this repoWeather
Leavesfly/Jimi
Get current weather and forecasts (no API key required). An agent skill from Leavesfly/Jimi.
API Design
Leavesfly/Jimi
RESTful API design best practices and conventions guide. An agent skill from Leavesfly/Jimi.
Database Design
Leavesfly/Jimi
数据库设计规范与优化指南
Git Commit Guide
Leavesfly/Jimi
Git 提交规范（Conventional Commits）
Unit Testing
Leavesfly/Jimi
Java单元测试编写指南（基于JUnit和Mockito）
Java Best Practices
Leavesfly/Jimi
Java 编码最佳实践与设计模式
Questions about Maven Troubleshoot
How do I install Maven Troubleshoot in Claude Code?
Run `npx skills add Leavesfly/Jimi --skill maven-troubleshoot -a claude-code`. Or copy the skill folder (src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot in Leavesfly/Jimi) into .claude/skills/maven-troubleshoot in your project. Claude Code loads it when a task matches its description.
How do I install Maven Troubleshoot in Codex?
Run `npx skills add Leavesfly/Jimi --skill maven-troubleshoot -a codex`. Or copy the skill folder (src/main/resources/plugins/jimi-dev-kit/skills/maven-troubleshoot in Leavesfly/Jimi) into .agents/skills/maven-troubleshoot in your project. Codex loads it when a task matches its description.
Can I use Maven Troubleshoot 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 Leavesfly/Jimi --skill maven-troubleshoot -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maven-troubleshoot, .gemini/skills/maven-troubleshoot, .github/skills/maven-troubleshoot and .opencode/skills/maven-troubleshoot in your project.
What does Maven Troubleshoot need to run?
Going by SKILL.md and its folder, Maven Troubleshoot needs the command-line tools its instructions call (mvn).
Does Maven Troubleshoot 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 Maven Troubleshoot 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 Maven Troubleshoot use?
No licence was found for Maven Troubleshoot or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Maven Troubleshoot use?
About 259 tokens (SKILL.md is roughly 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 Maven Troubleshoot?
Skills that share tags, products or a category with Maven Troubleshoot: Startup It Troubleshooting (sickn33/agentic-awesome-skills, 47k stars), Troubleshooting (cartography-cncf/cartography, 4.1k stars), Power Bi Performance Troubleshooting (github/awesome-copilot, 40k stars) and WxJava Troubleshooter (binarywang/WxJava, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Maven Troubleshoot?
Leavesfly (a GitHub user) maintains it in Leavesfly/Jimi, which has 237 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on August 19, 2026.
Source: Leavesfly/Jimi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.