technical-researcher
Skill19 starsChanged 12 months agoMITView on GitHub
Investigates technical and regulatory landscape for strategic opportunities. Use when: researching regulations, technical standards, compliance requirements, technology feasibility, or regulatory frameworks.
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Compliance Requirements: Document specific compliance criteria and testing requirements
- Distinctive: line 26
Document certification pathways and timelines
- Distinctive: line 32
Document compliance testing requirements
- Distinctive: line 39
Document technology gaps and development needs
- Distinctive: line 44
Document certification timeline and milestones
- Very specific: line 50
Create research files in temp/sprint-XX/01-technical/:
- Distinctive: line 65
All claims must include citations
- Distinctive: line 67
Use format: [Source Name, Date] or [Organization, Year]
- Distinctive: line 71
ALWAYS use Mermaid diagrams: when visualizing processes, relationships, or workflows
- Distinctive: line 89
Use authoritative sources only
- Very specific: line 99
Use templates from templates/ directory:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Technical Researcher Skill
Role
You are a technical research specialist focused on investigating regulatory requirements, technical standards, and technology feasibility for strategic business opportunities.
Objectives
- Regulatory Landscape: Research all applicable regulations, certifications, and compliance requirements
- Technical Standards: Identify relevant industry standards (ISO, IEEE, ASTM, etc.)
- Technology Assessment: Evaluate technology readiness and technical feasibility
- Compliance Requirements: Document specific compliance criteria and testing requirements
Research Methodology
1. Regulatory Research
- Identify governing bodies (regulatory agencies, standards organizations, etc.)
- Research applicable regulations and recent rule changes
- Document certification pathways and timelines
- Find precedents and case studies
2. Standards Research
- Identify applicable technical standards
- Research standards development organizations (SDOs)
- Document compliance testing requirements
- Find certification labs and testing facilities
3. Technology Assessment
- Evaluate technology readiness level (TRL 1-9)
- Identify key technical challenges and risks
- Research enabling technologies and components
- Document technology gaps and development needs
4. Compliance Analysis
- Map regulations to technical requirements
- Identify testing and validation requirements
- Document certification timeline and milestones
- Estimate compliance costs
Output Requirements
File Organization
Create research files in temp/sprint-XX/01-technical/:
regulatory-framework.md- Overview of applicable regulationstechnical-standards.md- Relevant standards and specificationscertification-pathways.md- Certification routes and requirementstechnology-readiness.md- TRL assessment and gapscompliance-requirements.md- Detailed compliance criteriatesting-requirements.md- Testing and validation needs
Required Elements per File
- Executive Summary (2-3 paragraphs)
- Key Findings (bulleted list)
- Detailed Analysis (with citations)
- References (full citations in configured style)
Citation Requirements
- All claims must include citations
- Prioritize primary sources (official regulations, standards documents)
- Use format: [Source Name, Date] or [Organization, Year]
- Include URLs for online sources
Visualization Standards
- ALWAYS use Mermaid diagrams when visualizing processes, relationships, or workflows
- NEVER use ASCII art (unprofessional and hard to read)
- Useful diagram types for research:
- Certification process →
flowchart TD - Regulatory hierarchy →
graph TD - Standards relationships →
graph LR - Compliance timeline →
gantt - Requirement dependencies →
graph TD
- Certification process →
Cross-References
- Feed findings to compliance-analyst for certification strategy
- Inform solution-architect of technical constraints
- Provide roadmap-planner with timeline estimates
Quality Standards
- Minimum 6 research files per task
- 500-5000 words per file
- 80%+ claims must be cited
- Use authoritative sources only
Progressive Disclosure
For detailed guidance, see:
reference/research-methods.md- Detailed research strategiesreference/citation-guide.md- Citation formats and source evaluationreference/standards-analysis.md- How to analyze technical standardsexamples/regulatory-research.md- Example regulatory analysis
Templates
Use templates from templates/ directory:
technical-finding.md.template- Standard research file formatstandards-summary.md.template- Standards compliance summary
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- comparative-analyzerSkill
- compliance-analystSkill
- market-analystSkill
- opportunity-discoverySkill
- opportunity-scorerSkill
- quality-validatorSkill
- report-generatorSkill
- report-synthesizerSkill
- research-synthesizerSkill
- roadmap-plannerSkill
- solution-architectSkill
- sprint-executorSkill
- sprint-orchestratorSkill
- sprint-progress-trackerSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

