problem-solver-specialist 1.0.0 Immutable snapshotLatest
Pinned to commit 5bd4f168edf7c18a8303cbfde20708ff62aabc4d, captured .
Download 1.0.0 source archive Choose something to compare with View commit on GitHub
More actions and subscriptions
Current package description (not historical)
Universal expert problem-solving agent specializing in complex debugging, mysterious runtime behavior, integration issues, and multi-layered technical challenges across any technology stack or project type. Uses advanced research methodologies including GitHub issues mining, Perplexity deep research, community solutions validation, browser automation testing, and multi-source documentation analysis. Proactively use for intricate bugs, cryptic error messages, performance anomalies, framework integration problems, legacy system compatibility issues, and any technical challenges requiring deep investigation across multiple knowledge sources. Project-agnostic and universally applicable.
Install
This version is listed in the verified marketplace awesome-claude-code-plugins (repository ccplugins/awesome-claude-code-plugins). Run these in Claude Code, in order:
- Add the marketplace
/plugin marketplace add ccplugins/awesome-claude-code-plugins - Install the plugin
/plugin install problem-solver-specialist@awesome-claude-code-plugins
These commands install the marketplace's current upstream state, not the pinned commit snapshot on this page; the two can differ.
Contents 1
Agent1
-
problem-solver-specialist
plugins/problem-solver-specialist/agents/problem-solver-specialist.mdPermalink
Nothing matches.
Dependencies, compatibility and skill declarations
Recorded dependencies 0
No dependency requirements were recorded from plugin.json or marketplace entries. Only manifest fields saved with the snapshot are shown here; dependency declarations in other files are outside the current collection scope.
Recorded compatibility
No compatibility requirement was recorded for this snapshot from plugin.json or a marketplace entry. Only manifest fields saved with the snapshot are shown here. Declarations in a skill's SKILL.md header are collected separately and, when present, shown on their own under “Skill file declarations”; they never overwrite or fill in this value.