deepresearch-readme

Creates, improves, and reviews GitHub OSS README files with structured Quickstart sections.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/j5ik2o/marp-ai-base --skill deepresearch-readme-j5ik2o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deepresearch-readme
Source: https://github.com/j5ik2o/marp-ai-base/tree/main/.agents/skills/deepresearch-readme
Command: npx skills add https://github.com/j5ik2o/marp-ai-base --skill deepresearch-readme-j5ik2o

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? GitHub project READMEs often bury setup instructions, lack a working Quickstart, or grow too long for readers to find what the project does and how to start. This Skill structures README creation, restructuring, and review around What/Why/How to start/Help/Maintainers so new users can run the project within minutes. ## Core Features & Use Cases - README Creation: Generates a new README from a template covering Highlights, Quickstart (Requirements/Install/Run), Usage, Documentation, Getting help, Contributing, and License. - README Review: Audits existing READMEs against a checklist with Critical/Warning/Info severity levels, flagging broken Quickstarts, missing sections, and weak docs links. - Documentation Splitting Guidance: Decides when long content should move to docs/ with relative links left in the README. - Use Case: A maintainer preparing an open-source CLI release asks for a README review; the Skill identifies that the install command is outdated and the Quickstart lacks a minimal run example, then rewrites those sections. ## Quick Start Ask the assistant to create or review a GitHub README for your project, for example: review my repository's README and fix the Quickstart section.

Frequently Asked Questions about deepresearch-readme

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

FAQPage Schema
How do I write a good GitHub README for an open source project?

Start with the project name as H1 and a one-to-two sentence value statement, then add a Quickstart with Requirements, Install, and Run steps. Follow with Usage, Documentation links, Getting help, Contributing, and License sections, moving long details into a docs/ folder.

How to review an existing README for missing sections?

Check the first view for a clear value statement, verify the Quickstart actually runs, and confirm core sections like Usage, Documentation, Getting help, Contributing, and License exist. Issues are graded Critical, Warning, or Info based on whether they block getting started.

What sections should a GitHub README include?

A solid README includes Highlights, Quickstart (Requirements, Install, Run), Usage with a minimal example, Documentation links, Getting help, Contributing, and License. Detailed explanations belong in docs/ with relative links from the README.

When should I split README content into a docs folder?

Split content when OS-specific install steps or long explanations bury the getting-started path. Keep only introduction-essential information in the README and use relative links to files like docs/installation.md for the rest.

Does the README template adapt to different project types?

Yes, the template includes adaptation notes per project type. Libraries lead Usage with a minimal API example, CLIs show multiple run commands, web apps state the startup URL and login, and GitHub Actions include a minimal uses: YAML snippet.