weekly-progress

Generate narrative weekly progress reports from Telegram posts, session logs, and tracker data.

9|Updated Sep 22, 2025
One-click install
npx skills add https://github.com/SolomonikVik/svaib --skill weekly-progress
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-progress
Source: https://github.com/SolomonikVik/svaib/tree/main/.claude/skills/weekly-progress
Command: npx skills add https://github.com/SolomonikVik/svaib --skill weekly-progress

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of a narrative weekly progress report from multiple project sources (Telegram posts, session logs, and a tracker), turning raw notes into a cohesive story rather than a pile of numbers. It ensures that every claim is grounded in source material and avoids fabrication, saving time for leadership and communications teams.

Core Features & Use Cases

  • Pulls content from Telegram posts, session logs, and tracker entries to build a weekly chronicle that reflects real events and outcomes.
  • Produces a structured narrative with sections for Lab, Product (Second Brain), Clients, Marketing, Website, and Knowledge, highlighting key milestones, losses, and learnings.
  • Maps data across channels to produce a readable, publish-ready summary suitable for internal reviews, investor updates, or public publication.

Use cases include weekly leadership updates, public blog-style recaps of progress, or internal post-mortems after a sprint.

Quick Start

Generate the weekly progress narrative by pulling Telegram posts, session-log entries, and tracker data for the target week and summarize them into a cohesive story.

Frequently Asked Questions about weekly-progress

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

FAQPage Schema
How do I generate a narrative weekly progress report from Telegram posts and session logs?

Generate a narrative weekly report by pulling Telegram posts, session logs, and tracker data to compose a cohesive story. This process fetches raw project notes and maps them into structured sections for Lab, Product, Clients, Marketing, Site, and Knowledge.

What is narrative project tracking and how does it differ from standard tracker updates?

Narrative project tracking turns raw notes and numbers into a cohesive story rather than a simple list of metrics. It maps data across channels to produce a readable, publish-ready summary highlighting milestones, losses, and learnings for stakeholders.

Can I use Telegram posts and session logs for public blog-style project recaps?

Yes, you can use Telegram posts and session logs for public blog-style project recaps. The output is a publish-ready summary suitable for public publication, internal reviews, or investor updates based on real events and outcomes.

What is the best way to structure a weekly project report for internal stakeholders?

The best way to structure a weekly project report is by dividing it into specific sections: Lab, Product, Clients, Marketing, Website, and Knowledge. This ensures milestones and learnings are categorized logically for stakeholders.

How do I ensure a weekly project summary avoids fabrication and stays grounded in source material?

To avoid fabrication in a weekly project summary, the narrative must be built exclusively from fetched Telegram posts, session logs, and tracker entries. This ensures every claim is grounded in source material and reflects real outcomes.