research

Query primary sources and official documentation to produce cited Markdown research reports.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/tonomb/personal-pnl --skill research-tonomb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/tonomb/personal-pnl/tree/main/.agents/skills/research
Command: npx skills add https://github.com/tonomb/personal-pnl --skill research-tonomb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of shallow or hallucinated information by forcing an agent to perform rigorous, source-backed investigations into technical or domain-specific questions.

Core Features & Use Cases

  • Primary Source Verification: Ensures all findings are traced back to official documentation, source code, or technical specifications rather than secondary summaries.
  • Structured Documentation: Automatically compiles research findings into a clean, cited Markdown file within the repository.
  • Use Case: Use this when you need to understand the implementation details of a specific API or library and want a reliable, documented summary saved directly to your project notes.

Quick Start

Ask the research skill to investigate the current best practices for implementing authentication in Cloudflare Workers by referencing the official documentation.

Frequently Asked Questions about research

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

FAQPage Schema
How do I generate cited research reports from official documentation?

To generate cited research reports, the skill queries primary sources and official documentation to compile findings into a clean, cited Markdown file. It requires autonomous web access and local file system write permissions to save the documentation.

What is the best way to verify technical information against primary sources?

Verifying technical information against primary sources is achieved by forcing the agent to trace all findings back to official documentation, source code, or technical specifications. This avoids shallow or hallucinated information from secondary summaries.

How can I automate the creation of cited Markdown documentation for software architecture decisions?

You can automate cited Markdown documentation by instructing the skill to investigate technical topics, which then automatically compiles deep-dive research findings into a structured, cited Markdown file directly within your repository.

Do I need web access and local file write permissions for deep-dive technical research?

Yes, deep-dive technical research requires autonomous agent access to web-based primary source materials to gather information, and local file system write permissions to save the structured documentation directly to your project notes.

When should I use primary source verification for knowledge management?

You should use primary source verification when you need to understand the implementation details of a specific API or library and want a reliable, documented summary saved directly to your project notes to support architectural decision-making.

Are there limitations to using autonomous agents for source-backed investigations?

The primary limitation of source-backed investigations is strict dependency on accessible web-based primary source materials; if official documentation is unavailable or restricted, the agent cannot generate a verified, high-trust research report.