research

Analyze primary sources to synthesize cited technical findings.

Updated Dec 17, 2025
One-click install
npx skills add https://github.com/Frantss/oxform --skill research-frantss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/Frantss/oxform/tree/main/.agents/skills/research
Command: npx skills add https://github.com/Frantss/oxform --skill research-frantss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of information fragmentation by automating the synthesis of technical documentation, source code, and specifications into a single, reliable reference document.

Core Features & Use Cases

  • Primary Source Verification: Ensures all findings are traced back to official documentation, source code, or technical specs rather than secondary summaries.
  • Automated Documentation: Generates structured Markdown reports that serve as a single source of truth for complex technical topics.
  • Use Case: Use this when you need to understand the internal architecture of a new library or require a comprehensive summary of an API's capabilities based on its actual source code.

Quick Start

Use the research skill to investigate the implementation details of the oxform core validation engine by analyzing the source code in the packages core directory.

Frequently Asked Questions about research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze primary sources like source code and official documentation for technical research?

To analyze primary sources for technical research, you investigate repository files and external documentation to synthesize cited findings. This ensures all technical claims are traced back to authoritative source material rather than secondary summaries.

What is the best way to synthesize technical specifications into a single reference document?

The best way to synthesize technical specifications is to automate the extraction of information from source code and official documentation. This generates a structured Markdown report that serves as a reliable single source of truth for complex topics.

Can I use automated documentation to understand the internal architecture of a new library?

Yes, you can use automated documentation to understand a new library's internal architecture. By analyzing the actual source code and technical specifications, it retrieves high-fidelity information to map out the implementation details accurately.

How do I verify that technical findings are backed by authoritative source material?

You verify technical findings by performing primary source verification against official documentation and source code. This high-fidelity retrieval process ensures every synthesized claim is backed by authoritative source material before generating a report.

When do I need primary source verification instead of relying on secondary summaries?

You need primary source verification when investigating technical questions that require high-fidelity retrieval and cited findings. It prevents information fragmentation by ensuring your technical writing references actual source code and specifications rather than secondary summaries.

Does the research skill require any external dependencies to synthesize cited findings?

No external dependencies are required to synthesize cited findings. The skill operates directly across repository-level files and external documentation to investigate technical questions and generate structured Markdown reports independently.