research-writing

Analyze reference projects to generate structured Markdown research reports with API extractions.

23|2|Updated Jun 9, 2025
One-click install
npx skills add https://github.com/kaptinlin/gozod --skill research-writing-kaptinlin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-writing
Source: https://github.com/kaptinlin/gozod/tree/main/.agents/skills/research-writing
Command: npx skills add https://github.com/kaptinlin/gozod --skill research-writing-kaptinlin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to synthesize insights from multiple reference projects, leading to slow decision-making and inconsistent recommendations.

Core Features & Use Cases

  • Analyze references in the .references directory to generate structured research reports with evidence, conclusions, and recommended actions.
  • Produce API extraction blocks, decision matrices, and interface design guidance to inform product decisions.
  • Support topic-driven analysis across multiple projects and produce template-compliant outputs for the .research/ directory.

Quick Start

Place reference projects into .references and run the workflow to generate a report in .research.

Frequently Asked Questions about research-writing

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

FAQPage Schema
How do I generate a structured research report from multiple reference projects?

To generate a structured research report, place your reference projects into a .references directory of submodules and run the workflow to output a template-compliant Markdown report into the .research directory.

Can I extract API designs and build a decision matrix from a list of topics?

Yes, you can extract API designs and build a decision matrix by providing a list of topics, which triggers an analysis of reference implementations to produce evidence-based conclusions and interface design guidance.

What do I need to set up before synthesizing insights from reference implementations?

Before synthesizing insights, you need to set up a .references directory containing your reference project submodules and define a list of topics for the topic-driven analysis.

How does evidence-based analysis work for feature comparisons across projects?

Evidence-based analysis works by examining reference projects to synthesize insights, generating structured research reports that include API extractions, decision matrices, and citation rules for informed design decisions.

What is the best way to inform product decisions using reference submodules?

The best way to inform product decisions is to analyze reference submodules to produce structured outputs, including decision matrices and API extraction blocks that provide evidence-based recommendations.

Are there limitations when running topic-driven analysis on reference directories?

Topic-driven analysis requires a properly structured .references directory of submodules and a defined list of topics to successfully generate template-compliant Markdown reports in the .research directory.