breakthrough-edu

@breakthrough-edu source repo

18 skills
0 followers
15 hours ago last updated

▌
Breakthrough Brand Strategy · breakthrough-edu bundle
Take a brand from seeded stubs to a real brand foundation inside a second-brain vault: the seven pillars in `<Brand>-Brand-Assets/Brand-Strategy/` carried off `status: empty` one lock at a time, with the 6Cs research and the founder's own convictions filed as dated evidence underneath them. Use when the owner starts or resumes the brand intake ("run the brand intake", "my brand rooms are empty", or a brand pillar stub sends them here), asks to work one pillar by name (positioning, DNA, personality, proposition, relationship, sensory cues, or the style pillar), or asks for the decode research on its own ("6Cs", "founder backbone"). NOT for writing marketing copy or a campaign, and NOT for changing the vault's law (that is breakthrough-vault-guardian).

0
installs
▌
Breakthrough Content Engine · breakthrough-edu bundle
内容策划引擎：给一个生意目标，产出一整档内容规划，人只审一张 seed sheet，其余机械推导。覆盖 FB · IG · 短视频（TikTok / Reels）· 小红书，写给马来西亚华人小生意老板。五个入口：规划一档内容 ("帮我规划这个月的内容", "这一档要发几支", "我该发什么内容", "plan my content")；先诊断不规划 ("我的内容为什么没人看")；收客人的原话进素材库 ("我捞到几条客人的话", "客人讲了一句")；记成绩 ("记一下成绩", "这篇的数据")；复盘 ("复盘一下", "这几周跑得怎样")。NOT for: 单篇文案代写（那不需要整条 pipeline，直接写就好）· 付费投放的 creative 测试（本引擎只管 organic，配比逻辑完全不同）· 品牌策略本身（这个引擎吃品牌策略的产物，不产出品牌策略）。

0
installs
▌
Breakthrough Meeting Scribe · breakthrough-edu bundle
Turn meeting audio into three artifacts (a corrected transcript, an HTML visual canvas, and a Markdown summary with AI insights), transcribed locally with Whisper on any platform: no cloud, no external transcription app. Use when the user hands over a meeting recording or wants meeting notes from one ("处理这个录音", "会议纪要", "把录音转成文字", or an audio file lands in the configured drop-zone), wants an existing transcript corrected or cleaned ("处理 transcript", "转录纠错", "转写文本", or a .txt lands in the drop-zone), wants a recording pulled from their connected PLAUD account ("process my Plaud recording", "从 Plaud 拿"), asks for edits to a transcript, canvas, or summary this skill just produced, or asks for cross-meeting Insights on their communication patterns instead of processing one recording ("analyze my meetings", "how do I come across in meetings", "分析我的沟通模式", "复盘我最近的会议", "跨会议分析").

0
installs
▌
Breakthrough Sop Builder · breakthrough-edu bundle
Turn a process that lives in the owner's head into a written SOP their staff can actually follow: one guided sitting ending in a markdown note with a step-by-step RACI table and a swimlane map filed beside it. Works with or without a second-brain vault. Use when the user wants a process documented as an SOP ("write an SOP", "document this process", "SOP for <anything>", "帮我写 SOP", "把流程变成 SOP"), and when they resume a draft left mid-sitting ("continue the SOP", "接着上次那个 SOP"). NOT for setting up a second brain, building a vault, capturing a business into rooms, weekly maintenance, or giving an AI a persona: those belong to the my-second-brain skill, which is installed and updated separately from this one.

0
installs
▌
Breakthrough Whatsapp Triage · breakthrough-edu bundle
Turns an overwhelming WhatsApp backlog into a one-page daily action board with a ready-to-edit draft reply for each conversation that actually needs the user today. Everything stays on their machine, and nothing is ever sent automatically. Use when the user wants their WhatsApp triaged ("triage my whatsapp", "help me clear whatsapp", or complaining about hundreds of unread chats), wants the one-time export set up ("set up whatsapp export"), asks for an update later the same day or to refresh a board built on a stale export, asks to look further back or pull in one older conversation ("go back a week", "show me the last month"), wants the drafts to sound like them ("set up my tone profile", "update my tone profile"), hits a run that failed and needs diagnosing, or asks why the board behaves the way it does (why a row copies instead of opening, where a conversation or voice note went). The read window stays narrow by default and widens only on the user's explicit ask.

0
installs
▌
Invoice Generator Guide · breakthrough-edu
Guides a person from a fresh clone of this repo to their own working invoice generator wired to their own Lark (or Feishu) Base, one verified step at a time. Trigger when the user says "build my invoice generator", "set up the invoice generator", "help me set this up", "wire this to my Lark Base", "connect my Base", "fix my invoice generator", "the notification is not working", "reset the demo", or otherwise asks to install, configure, resume, troubleshoot, or reset this project. Runs entirely inside the cloned repo.

0
installs
▌
Social Video Transcript · breakthrough-edu bundle
Turn a short-video link from Douyin (抖音), Xiaohongshu / RED (小红书), Instagram, Facebook, or TikTok into a clean, readable markdown transcript, fully local, free, on Apple Silicon macOS. The user pastes a video link or share-text; the skill downloads the video, extracts audio, transcribes locally with Whisper large-v3 (Apple Neural Engine via whisperkit-cli, auto-detecting the language), light-cleans the raw ASR into readable prose (fixing the homophone / proper-noun errors Whisper makes, using the video's own title/topic as context), saves ONE markdown file to an output folder, deletes the downloaded media, and stops. MUST trigger when the user provides a Douyin / Xiaohongshu / 小红书 / RED / Instagram / Facebook / TikTok video link or share-text, or says "转写这个视频", "把这个视频转成文字", "transcribe this video", "transcribe this reel", "这个视频讲什么", "抖音转写", "小红书转写", "transcribe this douyin / xhs / instagram / facebook / tiktok", "social-video-transcript", or pastes a douyin.com / xiaohongshu.com / xhslink.com / instagram.com

0
installs
▌
Youtube Transcript Ingestion · breakthrough-edu bundle
Batch-grab transcripts from any YouTube channel and save them as readable markdown files with clean frontmatter. Guided 5-step flow -- channel, keyword + date filter, output folder, optional context-delta comparison, rate-limit strategy -- using yt-dlp for metadata and markitdown for transcripts. Optionally compares results against your existing notes to surface only what is genuinely new. Trigger phrases -- grab YouTube transcripts, ingest YouTube channel, yt-dlp transcripts, markitdown YouTube, research a creator's videos, build a corpus from a channel, filter content overload from a channel.

0
installs
▌
Breakthrough Base Schema Design · breakthrough-edu bundle
Design a Lark Base for the user's business through a guided interview: find the one unit of work the business repeats, then derive the tables, links, formulas and a phased build order from the numbers the owner actually wants to see. Ends with a Base Blueprint document plus an acceptance test, ready to hand to whoever builds it. Use when the user wants a database designed for their business ("design my Lark Base", "what tables do I need", "help me build a database for my company", "帮我设计多维表格", "我的业务要怎么建表"), when their existing base has become one giant table and they want it restructured, or when they are unsure whether something should be a field, a select, or its own table. NOT for physically building or editing a Base via API or lark-cli (this skill produces the blueprint; building is a separate job), NOT for turning an already-filled database into reports or dashboards (that is breakthrough-database-to-dashboard), and NOT for setting up a second-brain vault (that is my-second-brain, installed separately).

0
installs
▌
Breakthrough Database To Dashboard · breakthrough-edu bundle
Turn the business data the user already has (Airtable, Notion, Google Sheets, Lark Base, Excel, CSV exports, or a database someone once set up for them) into three things in one sitting: a plain-language account of what their database actually records, a findings list of data problems and blind spots, and a one-page dashboard answering the single most urgent money question, with alerts ranked by money at risk. Use when the user wants a dashboard or a read of their data ("build me a dashboard", "turn my spreadsheet into a dashboard", "what is my data telling me", "帮我做仪表板", "分析我的数据/表格"), pastes a link or drops files from one of those products and asks what the data says, or returns with a fresh export to refresh a page built earlier. NOT for designing or restructuring the database itself (that is breakthrough-base-schema-design), NOT for setting up a second brain or vault, and NOT a live auto-updating dashboard: every page is a snapshot of one export.

0
installs
▌
Breakthrough Performance Analysis · breakthrough-edu bundle
Weekly read of your Meta-ads performance Base: names in plain language whose problem this week's numbers are, and refuses to advise when an opening check fails. Installing the Base is /breakthrough-performance-db-setup.

0
installs
▌
Breakthrough Performance DB Setup · breakthrough-edu bundle
One-time install of your Meta ad performance database: copy the template Lark Base, wire the daily sync to your own Meta token, reconcile it against Ads Manager, and leave a pointer note in your vault. The weekly read of the installed Base is /breakthrough-performance-analysis.

0
installs
▌
My Second Brain · breakthrough-edu bundle
Build and run a business owner's second brain: one vault, two wings (personal + four-layer business), operated through Claude Code with Obsidian as the viewing deck. Routes every entry to one of four modes: Setup, Capture, Distill, Create-My-Jarvis. Use when the user wants a second brain built or their business knowledge organized into a vault ("set up my second brain"), or asks to continue an installation paused between stations ("continue setup", "next station"), wants to move their business in one room at a time ("capture", "move in a room"), asks for the weekly maintenance ritual ("distill", "tidy my vault", "weekly review"), wants their AI given a persona ("create my jarvis"), or asks for a retrofit an older vault lacks: the safety lock, session memory ("make my sessions searchable"), the maintenance doorbell ("update my maintenance doorbell"), the boot gate ("upgrade my command base"), or the Command Deck ("rebuild my deck", "fix my deck", "add my command deck", "my dashboard is empty").

0
installs
▌
Breakthrough Method Builder · breakthrough-edu
Write down how the owner does a kind of work: one Method note when a piece of work closes, a Playbook when the owner asks for one (composed from the folder's methods, or ⭐ dictated straight from how they already work when there are none, day one included), and the door of any folder born along the way. Runs when the owner calls this skill by name, asks for a method or a playbook to be written, or when the session was told at the outset to write a Method when the work closed. ⛔ Work-closing phrasing alone ("we are done", "that went well", "wrap up") is not a request for this skill; session closeout belongs to breakthrough-session-report. NOT for a pit that hurt (that is a Lesson, written at session closeout), NOT for a call that still stands (that is a decision), NOT for dead repeatable steps (that is breakthrough-sop-builder), and ⛔ NOT the runner of a playbook's four beats: those live in the door itself and run without any skill (doctrine section 9.3).

0
installs
▌
Breakthrough Session Report · breakthrough-edu
Close out a working session in the owner's second-brain vault while whoever was in it still remembers: the Lesson it earned, the decision made but never written, anything reusable, and one baton note in `00_Inbox/` for the next session to read and archive. Use when the user says "wrap up", "close out", or otherwise ends a working session that produced something worth keeping. ⛔ NOT the end of the day, which is the owner's own command-base skill ("compile", "done for today"): a day ending is not a piece of work ending, and the two have separate words. NOT the weekly maintenance ritual (that is my-second-brain's distill mode), and NOT the place to write a Method (that is breakthrough-method-builder, which runs when a piece of WORK closes, not when a session does).

0
installs
▌
Breakthrough Vault Guardian · breakthrough-edu bundle
Change the law of this vault (99_Meta/structure-doctrine.md) without breaking the house that runs on it: one amendment, every file that moves with it, the cost said out loud, edits only on the owner's yes, then proof the guard still reads. Use for any of the three amendment shapes: a new wing ("I want to add a second business"), a family or key the law has not got ("there is no family for this", "add a new type of note"), or a rule loosened or dropped ("make this key optional", "I don't want to fill in X every time"). Also fires the moment the frontmatter guard refuses a note ("the guard blocked my note"). NOT for filing a single note (doctrine section 0's decision tree), NOT for the weekly sweep (maintenance), NOT for an SOP or a project plan, and NEVER for the product's own template: only this vault's own copy of the law.

0
installs
▌
Breakthrough Vault Migrator · breakthrough-edu
Move an existing body of files into this vault without breaking the relationships between the documents: freeze the boundary, get the owner's ruling on a mapping, then move in batches, rewriting links as it goes, and resume from 99_Meta/migration-progress.md across as many sittings as it takes. Use when an owner arrives with an old vault, an export (Notion, Evernote, Google Drive), or years of loose folders they want living in this vault ("migrate my old notes", "move my old vault in"), when they resume one in flight ("continue the migration", "where were we"), or when the material already IS a working vault that setup deliberately left untouched. NOT for material that carries no links and no structure worth keeping and can be mapped and moved in one sitting (that is Capture's bulk move-in). NOT for building the vault (setup runs first and this skill will not scaffold). NOT for transactional rows exports, which never enter a vault at all (doctrine section 4, law 1). NOT for changing the law to fit the incomin

0
installs
▌
Breakthrough Project Consultant · breakthrough-edu
Think a project through with an owner before they build it, then leave behind only the working files that project actually earns, usually a bare brief and nothing else. Use when the user wants to plan, scope, or kick off a piece of work that will outlive one sitting ("help me plan X", "kick off a project"), when a project is stuck or going nowhere and needs an honest restart, when they ask for a handoff or a brain dump of a project, or when a project's brief flips to done or killed and its file set needs reconciling. NOT for filing a note, NOT for writing an SOP (that is breakthrough-sop-builder), NOT for the daily operating rhythm (that is the owner's command-base skill), and NOT for writing up methodology (that is breakthrough-method-builder).

0
installs

18 published skills