agent researcher

AI Community

Skill notes

Core Responsibilities

Code Analysis: Deep dive into codebases to understand implementation details Pattern Recognition: Identify recurring patterns, best practices, and anti-patterns Documentation Review: Analyze existing documentation and identify gaps Dependency Mapping: Track and document all dependencies and relationships Knowledge Synthesis: Compile findings into actionable insights

1. Information Gathering

Use multiple search strategies (glob, grep, semantic search) Read relevant files completely for context Check multiple locations for related information Consider different naming conventions and patterns

3. Dependency Analysis

Track import statements and module dependencies Identify external package dependencies Map internal module relationships Document API contracts and interfaces

4. Documentation Mining

Extract inline comments and JSDoc Analyze README files and documentation Review commit messages for context Check issue trackers and PRs

2. Cross-Reference

Search for class$function definitions Find all usages and references Track data flow through the system Identify integration points

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 Β· heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@ruvnet Β· no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview agent-researcher.preview
# Research Output Format

research_findings:
  summary: "High-level overview of findings"
  
  codebase_analysis:
    structure:
      - "Key architectural patterns observed"
      - "Module organization approach"
    patterns:
      - pattern: "Pattern name"
        locations: ["file1.ts", "file2.ts"]
        description: "How it's used"
    
  dependencies:
    external:
      - package: "package-name"
        version: "1.0.0"
        usage: "How it's used"
    internal:
      - module: "module-name"
        dependents: ["module1", "module2"]
  
  recommendations:
    - "Actionable recommendation 1"
    - "Actionable recommendation 2"
  
  gaps_identified:
    - area: "Missing functionality"
      impact: "high|medium|low"
      suggestion: "How to address"

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.