Run Unit Tests
Azure/cosmos-explorer
Run unit tests for the Cosmos Explorer project. An agent skill from Azure/cosmos-explorer.
Parse build errors, test failures, type-check output, and validation logs into structured data.
Install Parse Error Logs
$ npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill parse-error-logs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit parse-error-logs --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/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/parse-error-logs .claude/skills/parse-error-logs && 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 "parse-error-logs" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/parse-error-logs into .claude/skills/parse-error-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parse-error-logs", 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/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/parse-error-logsType 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 maslennikov-ig/claude-code-orchestrator-kit --skill parse-error-logs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit parse-error-logs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/parse-error-logs .agents/skills/parse-error-logs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "parse-error-logs" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/parse-error-logs into .agents/skills/parse-error-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parse-error-logs", 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 maslennikov-ig/claude-code-orchestrator-kit --skill parse-error-logs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit parse-error-logs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/parse-error-logs .cursor/skills/parse-error-logs && 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 "parse-error-logs" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/parse-error-logs into .cursor/skills/parse-error-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parse-error-logs", 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/maslennikov-ig/claude-code-orchestrator-kit.git --path .claude/skills/parse-error-logs--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 maslennikov-ig/claude-code-orchestrator-kit --skill parse-error-logs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit parse-error-logs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/parse-error-logs .gemini/skills/parse-error-logs && 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 "parse-error-logs" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/parse-error-logs into .gemini/skills/parse-error-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parse-error-logs", 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 maslennikov-ig/claude-code-orchestrator-kit parse-error-logsInstalls 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 maslennikov-ig/claude-code-orchestrator-kit --skill parse-error-logs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/parse-error-logs .github/skills/parse-error-logs && 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 "parse-error-logs" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/parse-error-logs into .github/skills/parse-error-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parse-error-logs", 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 maslennikov-ig/claude-code-orchestrator-kit --skill parse-error-logs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit parse-error-logs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/parse-error-logs .opencode/skills/parse-error-logs && 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 "parse-error-logs" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/parse-error-logs into .opencode/skills/parse-error-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parse-error-logs", 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
parse-error-logs- GitHub stars
- 260
- Token cost
- ~1.5k tokens
- SKILL.md length
- 281 words
- Files
- 2
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Parse build errors, test failures, type-check output, and validation logs into structured data.
- Works in 5 steps: Receive Raw Output → Identify Error Patterns → Extract Error Details → …
- Processing npm/pnpm output
- SKILL.md covers When to Use, Instructions, Error Handling and Examples, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Parse Error Logs is an agent skill from maslennikov-ig/claude-code-orchestrator-kit. Parse build errors, test failures, type-check output, and validation logs into structured data. Use when processing npm/pnpm output, TypeScript errors, Jest failures, or any validation command results for quality gates.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `patterns.json`).
It sits in Testing & QA, covering Failing and flaky tests, Schema markup and Unit testing. It works with Jest, TypeScript, npm and pnpm. The repository describes itself as: 🎼 Turn Claude Code into a production powerhouse. 33+ AI agents automate bug fixing, security scanning, and dependency management. 19 slash commands, 6 MCP configs (600-5000…
When your agent uses it
- Processing npm/pnpm output
- TypeScript errors
- Any validation command results for quality gates
Example prompts
- “/parse-error-logs”
Requirements
- Pre-approved tools (allowed-tools): Read
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Receive Raw Output
- Identify Error Patterns
- Extract Error Details
- Categorize and Count
- Return Structured Data
What it can do on your machine
Read from SKILL.md and the folder at commit 8c3b576. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Read
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 json).
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
Parse Error Logs loads about 1.5k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 281 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 281 words (~1,479 tokens).
“Parse error and validation output from various tools into structured, actionable data.”
- name
- parse-error-logs
- allowed-tools
- Read
Files
SKILL.md and 1 other file in .claude/skills/parse-error-logs of maslennikov-ig/claude-code-orchestrator-kit.
- SKILL.md
- patterns.json
Open the folder on GitHubat commit 8c3b576
Compare with similar skills
Parse Error Logs 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 |
|---|---|---|---|---|---|---|
| Parse Error Logs this skillmaslennikov-ig/claude-code-orchestrator-kit | 260 | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Run Unit TestsAzure/cosmos-explorer | 131 | — | ~638 | Automated safety check: Pass | MIT | |
| ClickUp CLI Testingkrodak/clickup-cli | 123 | — | ~1.4k | Automated safety check: Notes | MIT | |
| Handsontable Unit Testinghandsontable/handsontable | 22k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Pump Testingnirholas/pump-fun-sdk | 134 | — | ~706 | Automated safety check: Pass | Custom licence | |
| Repo Healthcheck Nodecommercetools/ui-kit | 154 | — | ~1.6k | Automated safety check: Notes | MIT |
Similar skills
- Official
ClickUp CLI Testing
krodak/clickup-cli
Explains how to run and extend the clickup-cli tests: unit tests with a mocked client, e2e tests against a real ClickUp workspace, and the fixture data they rely on.
Handsontable Unit Testing
handsontable/handsontable
Conventions for Handsontable's Jest unit and TypeScript type tests: where files go, how to run them, mocking limits and when to write an E2E test instead.
Pump Testing
nirholas/pump-fun-sdk
Multi-language test infrastructure for the Pump SDK — Rust unit/integration/security/performance tests, TypeScript Jest tests, Python fuzz tests, shell test orchestration, Criterion benchmarks, and…
Repo Healthcheck Node
commercetools/ui-kit
Verify a Node.js/TypeScript repo's development environment is correctly set up.
Antfu
oyjt/uniapp-vue3-template
Anthony Fu's {Opinionated} preferences and best practices for web development
More from maslennikov-ig/claude-code-orchestrator-kit
All 29 skills in this repoSenior Architect Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin…
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
Senior Prompt Engineer
maslennikov-ig/claude-code-orchestrator-kit
Provides reference guides and Python scripts for prompt optimization, RAG evaluation, and agent orchestration when building or tuning LLM systems.
Priority Score Calculator
maslennikov-ig/claude-code-orchestrator-kit
Scores a bug, issue or task from severity, impact and likelihood on a 0-30 scale and maps the total to a P0 to P4 priority category with a suggested action.
Code Review with Beads Tasks
maslennikov-ig/claude-code-orchestrator-kit
Reviews staged changes, a branch, a PR or a path for bugs, security gaps and performance issues, then writes an evidence-based report and creates Beads tasks.
Semantic Version Parser
maslennikov-ig/claude-code-orchestrator-kit
Extracts and validates semantic version strings from mixed text, parsing major, minor, patch, prerelease and build components with a fixed regular expression.
Related
Works with
Categories
Questions about Parse Error Logs
What does Parse Error Logs do?
Parse build errors, test failures, type-check output, and validation logs into structured data. Parse Error Logs is an agent skill from maslennikov-ig/claude-code-orchestrator-kit. Parse build errors, test failures, type-check output, and validation logs into structured data.
When should I use Parse Error Logs?
Parse Error Logs fits situations like: processing npm/pnpm output; typeScript errors; any validation command results for quality gates.
How do I install Parse Error Logs in Claude Code?
Run `npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill parse-error-logs -a claude-code`. Or copy the skill folder (.claude/skills/parse-error-logs in maslennikov-ig/claude-code-orchestrator-kit) into .claude/skills/parse-error-logs in your project. Claude Code loads it when a task matches its description.
How do I install Parse Error Logs in Codex?
Run `npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill parse-error-logs -a codex`. Or copy the skill folder (.claude/skills/parse-error-logs in maslennikov-ig/claude-code-orchestrator-kit) into .agents/skills/parse-error-logs in your project. Codex loads it when a task matches its description.
Can I use Parse Error Logs 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 maslennikov-ig/claude-code-orchestrator-kit --skill parse-error-logs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/parse-error-logs, .gemini/skills/parse-error-logs, .github/skills/parse-error-logs and .opencode/skills/parse-error-logs in your project.
What does Parse Error Logs need to run?
SKILL.md names no scripts, command-line tools or credentials: Parse Error Logs is instructions for the agent only. Its frontmatter pre-approves these tools: Read.
Does Parse Error Logs 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 Parse Error Logs 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 Parse Error Logs use?
Parse Error Logs has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Parse Error Logs use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 Parse Error Logs?
Skills that share tags, products or a category with Parse Error Logs: Run Unit Tests (Azure/cosmos-explorer, 131 stars), ClickUp CLI Testing (krodak/clickup-cli, 123 stars), Handsontable Unit Testing (handsontable/handsontable, 22k stars) and Pump Testing (nirholas/pump-fun-sdk, 134 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Parse Error Logs?
maslennikov-ig (a GitHub user) maintains it in maslennikov-ig/claude-code-orchestrator-kit, which has 260 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on March 5, 2026.
Source: maslennikov-ig/claude-code-orchestrator-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.