enuno/claude-command-and-control/researcher-role-skill

Claude Code and agent skill by enuno/claude-command-and-control

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Professional technical solutions research skill for investigating technologies, analyzing best practices, evaluating feasibility, and producing comprehensive reports with actionable recommendations for development initiatives.

Install

npx vskill@latest install enuno/claude-command-and-control/researcher-role-skill

SKILL.md

Researcher Role Skill

Description

Gather information, analyze relevant subject matter, research technologies and best practices, and produce comprehensive reports with recommendations for application improvements, new features, and development initiatives. This skill implements professional research practices including methodology design, comparative analysis, and evidence-based recommendations.

When to Use This Skill

  • Evaluating technology options (frameworks, libraries, tools)
  • Conducting competitive analysis and industry research
  • Investigating best practices and proven patterns
  • Analyzing feature feasibility and complexity
  • Deep-diving into technical challenges and solutions
  • Monitoring emerging technologies and trends
  • Producing recommendation reports for decision-makers

When NOT to Use This Skill

  • For code implementation (use builder-role-skill)
  • For system architecture design (use architect-role-skill)
  • For infrastructure deployment (use devops-role-skill)
  • For documentation writing (use scribe-role-skill)

Prerequisites

  • Clear research question or problem statement
  • Access to project context (DEVELOPMENT_PLAN, ARCHITECTURE)
  • Internet access for external research
  • Stakeholder requirements and constraints

Workflow

Phase 1: Technology Evaluation

Research and compare technology options for informed decision-making.

Step 1.1: Research Request Analysis

Load context files:
- DEVELOPMENT_PLAN.md (overall plan)
- ARCHITECTURE.md (current system)
- TODO.md (pending work)
- User request or issue description

Step 1.2: Define Research Scope

Create RESEARCH_BRIEF.md:

markdown
# Research Brief: [Topic]
## Research Question
[Clear, focused question to answer]
## Context
-Current state: [What exists now]
-Problem: [What needs solving]
-Constraints: [Technical, budget, timeline limitations]
-Success criteria: [What makes a solution acceptable]
## Research Scope
**In Scope**:
-[Specific area 1]
-[Specific area 2]
**Out of Scope**:
-[What we're NOT investigating]
## Stakeholders
-Requestor: [Name/Role]
-Decision makers: [Names/Roles]
-Implementation team: [Names/Roles]
## Timeline
-Research deadline: [Date]
-Decision deadline: [Date]
-Implementation target: [Date]
## Deliverables
-[ ] Technology comparison matrix
-[ ] Proof of concept (if needed)
-[ ] Implementation plan
-[ ] Risk assessment
-[ ] Final recommendation

Step 1.3: Conduct Research

Information Sources
  1. Official Documentation
  • Read official docs, guides, API references
  • Check version compatibility and support lifecycle
  • Review migration guides and breaking changes
  1. Community Resources
  • GitHub repositories (stars, issues, PR activity)
  • Stack Overflow discussions and common problems
  • Reddit, HackerNews, dev.to community sentiment
  • Conference talks and technical blog posts
  1. Benchmarks and Performance
  • Published benchmarks and performance studies
  • Real-world case studies
  • Load testing results
  1. Security and Compliance
  • CVE databases for known vulnerabilities
  • Security audit reports
  • Compliance certifications
  • License compatibility
Research Template
markdown
## Technology: [Name]
### Overview
-**Purpose**: [What it does]
-**Current Version**: [X.Y.Z]
-**Release Date**: [Date]
-**License**: [Type]
-**Maintainer**: [Organization/Individual]
### Key Features
-Feature 1: [Description]
-Feature 2: [Description]
-Feature 3: [Description]
### Pros
-✅ [Advantage 1 with evidence]
-✅ [Advantage 2 with evidence]
-✅ [Advantage 3 with evidence]
### Cons
-❌ [Disadvantage 1 with evidence]
-❌ [Disadvantage 2 with evidence]
-❌ [Disadvantage 3 with evidence]
### Performance
-Benchmark: [Metric with source]
-Scalability: [Evidence]
-Resource usage: [Data]
### Community & Support
-GitHub stars: [Count]
-Contributors: [Count]
-Open issues: [Count]
-Recent activity: [Assessment]
-Stack Overflow questions: [Count]
-Community size: [Assessment]
### Security
-Known vulnerabilities: [Count/Details]
-Security track record: [Assessment]
-Last security audit: [Date]
### Integration & Compatibility
-Works with: [List compatible technologies]
-Conflicts with: [List incompatibilities]
-Migration path from current: [Assessment]
### Learning Curve
-Documentation quality: [Rating/Assessment]
-Onboarding time: [Estimate]
-Team expertise: [Current level]
-Training resources: [Availability]
### Cost Analysis
-Licensing: [Free/Paid details]
-Infrastructure costs: [Estimates]
-Maintenance costs: [Estimates]
-Training costs: [Estimates]
-**Total Cost of Ownership**: [Estimate]
### Sources
1.[Source 1 with URL]
2.[Source 2 with URL]
3.[Source 3 with URL]

Step 1.4: Comparative Analysis

Create comparison matrix:

markdown
# Technology Comparison: [Use Case]
## Evaluation Criteria
| Criterion | Weight | Option A | Option B | Option C |
|-----------|--------|----------|----------|----------|
| Performance | 25% | 8/10 | 9/10 | 7/10 |
| Ease of Use | 20% | 7/10 | 6/10 | 9/10 |
| Community Support | 15% | 9/10 | 7/10 | 6/10 |
| Security | 20% | 8/10 | 9/10 | 7/10 |
| Cost | 10% | 6/10 | 8/10 | 9/10 |
| Integration | 10% | 7/10 | 8/10 | 6/10 |
| **Weighted Score** | | **7.7** | **8.0** | **7.4** |
## Detailed Comparison
### Performance
**Winner**: Option B
-Option A: [Specific performance metrics]
-Option B: [Specific performance metrics] ✅
-Option C: [Specific performance metrics]
**Evidence**: [Benchmark sources and data]
### Ease of Use
**Winner**: Option C
-Option A: [Developer experience assessment]
-Option B: [Developer experience assessment]
-Option C: [Developer experience assessment] ✅
**Evidence**: [Developer surveys, documentation quality]
[Continue for each criterion...]
## Risk Assessment
### Option A Risks
-**High**: [Risk with mitigation]
-**Medium**: [Risk with mitigation]
-**Low**: [Risk with mitigation]
### Option B Risks
-**High**: [Risk with mitigation]
-**Medium**: [Risk with mitigation]
-**Low**: [Risk with mitigation]
### Option C Risks
-**High**: [Risk with mitigation]
-**Medium**: [Risk with mitigation]
-**Low**: [Risk with mitigation]

Step 1.5: Proof of Concept (if needed)

markdown
# Proof of Concept: [Technology]
## Objective
Validate [specific capability] in our environment
## Approach
1.Setup: [Steps to configure]
2.Implementation: [What we built]
3.Testing: [How we validated]
4.Measurement: [Metrics collected]
## Results
### Success Criteria
-[Criterion 1]: ✅ PASSED / ❌ FAILED
-[Criterion 2]: ✅ PASSED / ❌ FAILED
-[Criterion 3]: ✅ PASSED / ❌ FAILED
### Performance Data
| Metric | Target | Actual | Status |
|--------|--------|--------|--------|
| Response time | <100ms | 85ms | ✅ |
| Throughput | >1000 rps | 1200 rps | ✅ |
| Error rate | <0.1% | 0.05% | ✅ |
### Observations
-[Finding 1]
-[Finding 2]
-[Finding 3]
### Code Sample

// POC implementation snippet [Relevant code demonstrating key concepts]

### Challenges Encountered
1. [Challenge and resolution]
2. [Challenge and resolution]
### Conclusion
[Assessment of POC results]

Step 1.6: Final Recommendation Report

Create RESEARCH_REPORT_[Topic].md:

markdown
# Research Report: [Topic]
**Date**: [YYYY-MM-DD]
**Researcher**: Researcher Agent
**Stakeholders**: [Names]
**Status**: Final / Draft
---
## Executive Summary
[2-3 paragraph summary covering:
-Research question
-Methodology
-Key findings
-Primary recommendation
-Expected impact]
---
## Research Context
### Background
[What prompted this research]
### Current State
[Description of existing solution/approach]
### Problem Statement
[What needs to be solved or improved]
### Constraints
-**Technical**: [Limitations]
-**Budget**: [Financial constraints]
-**Timeline**: [Time constraints]
-**Team**: [Skill/resource constraints]
---
## Research Methodology
### Approach
[How research was conducted]
### Sources Consulted
1.[Source type 1]: [Count] sources
2.[Source type 2]: [Count] sources
3.[Source type 3]: [Count] sources
### Evaluation Criteria
[How options were assessed]
---
## Findings
### Options Evaluated
1.**Option A - [Name]**
-Summary: [Brief description]
-Score: [X/10]
-Best for: [Use case]
2.**Option B - [Name]**
-Summary: [Brief description]
-Score: [X/10]
-Best for: [Use case]
3.**Option C - [Name]**
-Summary: [Brief description]
-Score: [X/10]
-Best for: [Use case]
### Key Insights
1.[Insight with supporting evidence]
2.[Insight with supporting evidence]
3.[Insight with supporting evidence]
### Industry Trends
[Relevant trends and their implications]
---
## Recommendation
### Primary Recommendation
**Recommended Solution**: [Option Name]
**Justification**:
1.[Reason 1 with evidence]
2.[Reason 2 with evidence]
3.[Reason 3 with evidence]
**Expected Benefits**:
-[Benefit 1 with quantification if possible]
-[Benefit 2 with quantification if possible]
-[Benefit 3 with quantification if possible]
**Known Limitations**:
-[Limitation 1 and mitigation]
-[Limitation 2 and mitigation]
### Alternative Recommendation
**If primary recommendation is not feasible**: [Option Name]
**When to consider**: [Circumstances]
---
## Implementation Considerations
### Technical Requirements
-Infrastructure: [What's needed]
-Dependencies: [Required packages/services]
-Integration points: [How it connects]
### Resource Requirements
-Development time: [Estimate]
-Team members: [Count and roles]
-Budget: [Estimate]
-Training: [Time and resources]
### Timeline
**Phase 1**: [Duration] - [Activities]
**Phase 2**: [Duration] - [Activities]
**Phase 3**: [Duration] - [Activities]
**Total Timeline**: [Duration]
### Risk Analysis
| Risk | Probability | Impact | Mitigation |
|------|------------|--------|------------|
| [Risk 1] | High/Med/Low | High/Med/Low | [Strategy] |
| [Risk 2] | High/Med/Low | High/Med/Low | [Strategy] |
| [Risk 3] | High/Med/Low | High/Med/Low | [Strategy] |
---
## Success Metrics
### Key Performance Indicators
1.**[Metric 1]**: [Baseline] → [Target]
2.**[Metric 2]**: [Baseline] → [Target]
3.**[Metric 3]**: [Baseline] → [Target]
### Measurement Plan
-Baseline measurement: [When and how]
-Progress tracking: [Frequency and method]
-Success evaluation: [Timeline and criteria]
---
## Next Steps
### Immediate Actions
1.[Action item] - Owner: [Role], Deadline: [Date]
2.[Action item] - Owner: [Role], Deadline: [Date]
3.[Action item] - Owner: [Role], Deadline: [Date]
### Decision Required
-**Decision maker**: [Name/Role]
-**Decision deadline**: [Date]
-**Decision criteria**: [What needs to be determined]
### Handoff
**To Architect** (or use architect-role-skill): [If architecture planning needed]
**To Builder** (or use builder-role-skill): [If prototyping needed]
**To DevOps** (or use devops-role-skill): [If infrastructure assessment needed]
---
## Appendices
### Appendix A: Detailed Comparison Matrix
[Comprehensive comparison table]
### Appendix B: Benchmark Data
[Detailed performance data]
### Appendix C: Security Analysis
[Security findings and assessments]
### Appendix D: Cost Breakdown
[Detailed cost analysis]
### Appendix E: References
1.[Source 1 with full citation]
2.[Source 2 with full citation]
3.[Source 3 with full citation]
[Continue numbering...]
---
**Document Version**: 1.0
**Last Updated**: [Date]
**Approved By**: [Name/Role] (if applicable)

Phase 2: Feature Research

Research and validate new feature proposals.

Step 2.1: Understand Feature Request

  • What problem does it solve?
  • Who are the users?
  • What's the expected behavior?
  • Any existing similar features in competitors?

Step 2.2: Research Similar Implementations

  • How do competitors implement this?
  • What are common patterns?
  • What are common pitfalls?

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
11
Repository forks
2
7-day trend score
12

Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 30 Mar 2026, 7 months ago.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/enuno/claude-command-and-control/researcher-role-skill/badge)](https://verified-skill.com/skills/enuno/claude-command-and-control/researcher-role-skill)

Something wrong with this skill or its page? Tell us.