skills.rest
MSBart2
MSBart2OFFICIAL
Explore all skills by this author →
GitHub

tech-talk-author

Generate tech talks from research notes to a README with citations.

2|9|Updated Dec 17, 2025
Search Tags:#automation#planning#research#readme#references#tech-talk
One-click install
npx skills add https://github.com/MSBart2/CopilotTraining --skill tech-talk-author
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-talk-author
Source: https://github.com/MSBart2/CopilotTraining/tree/main/.github/skills/tech-talk-author
Command: npx skills add https://github.com/MSBart2/CopilotTraining --skill tech-talk-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates tech talks from research notes to a publish-ready README, using the same phased workflow as the GitHub Issue pipeline, and producing artifacts at each stage.

Core Features & Use Cases

  • Follows a four-phase workflow (Research -> Plan -> Build -> Review) to produce research.md, plan.md, and README.md.
  • Produces intermediate artifacts before the final deliverable to enable review and refinement.
  • Use cases include preparing tech talks for internal teams, client engagements, or community talks with properly cited references.

Quick Start

Create a tech talk for a topic using a set of URLs.

Frequently Asked Questions about tech-talk-author

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

FAQPage Schema
How do I generate a tech talk from research notes to a README?▼

To generate a tech talk from research notes to a README, follow a four-phase workflow that produces research.md, plan.md, and a final README.md with citations. The process pauses for review between each phase to allow artifact refinement.

What is the process for preparing a technical presentation with citations?▼

Preparing a technical presentation with citations involves a four-phase workflow: Research, Plan, Build, and Review. It generates intermediate planning artifacts and a final README containing 8-15 properly formatted inline citations and references.

Can I create a tech talk README for client engagements and internal teams?▼

Yes, you can create a tech talk README for client engagements and internal teams. The workflow is designed for these contexts, producing structured research notes and a final README suitable for community presentations and technical audiences.

How many references do I need for a tech talk README?▼

A tech talk README requires 8-15 references with inline citations. These references are gathered during the Research phase and formatted into the final README during the Build phase to ensure proper attribution.

Does the tech talk workflow pause for plan and research review?▼

Yes, the tech talk workflow pauses for review between phases. This ensures you can validate intermediate artifacts like research.md and plan.md before generating the final README, maintaining quality control throughout the process.

What's the best way to structure a technical talk using markdown templates?▼

The best way to structure a technical talk using markdown templates is to follow the tech-talks/TEMPLATE.md structure. This ensures the final README and intermediate planning artifacts maintain a consistent, reviewable format across presentations.

Related Skills

Explore More Education & Research Skills→
CharGrnmnCharGrnmn
1

gpd-research-phase

Initiate a physics research phase and compile findings into RESEARCH.md.

Community
Advanced
jawwad-alijawwad-ali
4

github-repo-seo

Optimize GitHub repository metadata, READMEs, and social previews for discoverability.

Community
Intermediate
erafaterafat
16

cite-them-all

Identify citation-worthy claims in Markdown manuscripts and search PubMed for supporting literature.

Community
Intermediate
KrystianYCSilvaKrystianYCSilva

markdown-expert

Create Markdown documentation with Mermaid diagrams and GFM tables.

Community
Intermediate