[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EJBKP4QJ1EXH0EBADY95GW":3,"skill-same:01M7EJBKP4QJ1EXH0EBADY95GW":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EJBKP4QJ1EXH0EBADY95GW","course-builder",null,"Designs a course for a group of learners (a class, cohort, workshop series, bootcamp or internal training): measurable outcomes, a module sequence with prerequisites, activities and assessments aligned to each outcome, a time budget that fits the hours available, and a rubric, then checks the plan with a script so no outcome goes untaught or unassessed. Use when someone is teaching others and asks for a curriculum, syllabus, course outline, module plan, cohort or workshop structure, or wants an existing course checked for gaps and overload, even if they never say \"curriculum\". Not for one person's own learning plan (use study-system), for being taught the topic (use topic-primer), or for marketing the course (use sales-copy).","arm-pz\u002Fcaffeinity-skills","arm-pz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F29532099?v=4","01M7EJ726AAB9GD0C5C5G9NJEG","Abdul Rahman","01M7EJ726X4ZD3R4ESGX90K47M",0,"MIT","https:\u002F\u002Fgithub.com\u002Farm-pz\u002Fcaffeinity-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcaffeinity\u002Fskills\u002Fcourse-builder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: course-builder\ndescription: >-\n  Designs a course for a group of learners (a class, cohort, workshop series, bootcamp or\n  internal training): measurable outcomes, a module sequence with prerequisites, activities and\n  assessments aligned to each outcome, a time budget that fits the hours available, and a rubric,\n  then checks the plan with a script so no outcome goes untaught or unassessed. Use when someone\n  is teaching others and asks for a curriculum, syllabus, course outline, module plan, cohort or\n  workshop structure, or wants an existing course checked for gaps and overload, even if they\n  never say \"curriculum\". Not for one person's own learning plan (use study-system), for being\n  taught the topic (use topic-primer), or for marketing the course (use sales-copy).\nversion: 1.0.0\n---\n\n# course-builder\n\nA course fails in two quiet ways: an outcome the syllabus promises that no session teaches or\ntests, and twelve hours of content packed into eight hours of class. Both are visible on paper\nbefore the first session. This skill writes the plan as data, so a script can find them.\n\nIt designs the course; it does not write every lesson. Lesson content goes to `topic-primer`\n(concept explanations) and `wordsmith` (handouts and slides copy).\n\n## Intake\n\nAsk in one message, and mark what you assumed if the teacher does not answer:\n\n1. **Who are the learners?** Level, what they can already do, how many, and why they are here.\n2. **What must they be able to do at the end?** Tasks, not topics (\"deploy a site\", not \"web hosting\").\n3. **How much time?** Number of sessions, length of each, and expected work between sessions.\n4. **Format.** In person, live online or self-paced; group size; tools learners will have.\n5. **Constraints.** Fixed exam or certification, required topics, accessibility needs.\n\nIf the teacher has run `topic-primer` or `study-system` on the subject, take their component map\nas the starting decomposition instead of re-deriving it.\n\n## Workflow\n\n1. **Write the outcomes.** 3 to 8 course outcomes, each a learner-observable verb plus a\n   condition (\"Given a broken deploy log, identify the failing step\"). Avoid unmeasurable verbs:\n   understand, know, learn, appreciate, be aware of. `references\u002Foutcomes.md` has a verb list by\n   level and examples.\n2. **Sequence the modules.** Order by prerequisite, not by the textbook. Each module names the\n   outcomes it teaches and the earlier modules it depends on. Start with the smallest end-to-end\n   version of the final task, then deepen.\n3. **Align every module.** For each module: one practice activity that rehearses the outcome and\n   one assessment that would show it was met (`references\u002Falignment.md`). An outcome with no\n   assessment is a promise nobody checks.\n4. **Budget the time.** Give each module hours for contact time and for work between sessions.\n   The total must fit what the intake gave; cut or merge modules rather than squeezing.\n5. **Write it as `course.json`** in the shape in `references\u002Falignment.md`, then run:\n\n       python scripts\u002Fcheck_course.py course.json\n\n   It fails on an outcome nobody teaches or assesses, a prerequisite on a later or unknown\n   module, and a plan over its hour budget; it warns on unmeasurable outcome verbs, modules with\n   no outcome or no assessment, and modules over a quarter of the budget. Fix every FAIL.\n6. **Render the syllabus** for learners from the checked JSON: outcomes, the module table\n   (title, what you will be able to do, hours, assessment), how grading works and the rubric.\n\n## Rules\n\n- **Outcomes first, content second.** A topic that serves no outcome is cut or marked optional.\n- **One assessment per outcome, at least.** Final projects may assess several; say which.\n- **Rubrics describe evidence.** Each level says what the work shows, not \"good\" or \"excellent\".\n- **No invented resources.** Do not cite a book, course, dataset or tool you are not confident\n  exists; mark anything not checked this session `[unverified]`.\n- **Respect the learners' time.** Between-session work is counted in the budget, not hidden.\n\n## Handoffs\n\n| Signal | Owner | What you send |\n| --- | --- | --- |\n| One learner's own plan, practice routine, revision schedule | `study-system` | the outcomes, restated as that learner's target skill |\n| The concepts of one module need explaining | `topic-primer` | the module's outcome and the learners' starting level |\n| Handout, slide or announcement copy | `wordsmith` | the syllabus and the voice wanted |\n| Selling the course or cohort | `sales-copy` | the outcomes and who the course is for |\n| Course pages or a policy for refunds | `paper-trail` | the price, refund window and what learners submit |\n\n## Report\n\nLead with the outcomes and the checker result. Then the module table, total hours against the\nbudget, any WARN kept and why, assumptions made at intake, and the one next action.\n`references\u002Ftrigger-cases.md` holds the hand-run trigger cases; open it when tuning this\ndescription.\n","# course-builder\n\nA course fails in two quiet ways: an outcome the syllabus promises that no session teaches or\ntests, and twelve hours of content packed into eight hours of class. Both are visible on paper\nbefore the first session. This skill writes the plan as data, so a script can find them.\n\nIt designs the course; it does not write every lesson. Lesson content goes to `topic-primer`\n(concept explanations) and `wordsmith` (handouts and slides copy).\n\n## Intake\n\nAsk in one message, and mark what you assumed if the teacher does not answer:\n\n1. **Who are the learners?** Level, what they can already do, how many, and why they are here.\n2. **What must they be able to do at the end?** Tasks, not topics (\"deploy a site\", not \"web hosting\").\n3. **How much time?** Number of sessions, length of each, and expected work between sessions.\n4. **Format.** In person, live online or self-paced; group size; tools learners will have.\n5. **Constraints.** Fixed exam or certification, required topics, accessibility needs.\n\nIf the teacher has run `topic-primer` or `study-system` on the subject, take their component map\nas the starting decomposition instead of re-deriving it.\n\n## Workflow\n\n1. **Write the outcomes.** 3 to 8 course outcomes, each a learner-observable verb plus a\n   condition (\"Given a broken deploy log, identify the failing step\"). Avoid unmeasurable verbs:\n   understand, know, learn, appreciate, be aware of. `references\u002Foutcomes.md` has a verb list by\n   level and examples.\n2. **Sequence the modules.** Order by prerequisite, not by the textbook. Each module names the\n   outcomes it teaches and the earlier modules it depends on. Start with the smallest end-to-end\n   version of the final task, then deepen.\n3. **Align every module.** For each module: one practice activity that rehearses the outcome and\n   one assessment that would show it was met (`references\u002Falignment.md`). An outcome with no\n   assessment is a promise nobody checks.\n4. **Budget the time.** Give each module hours for contact time and for work between sessions.\n   The total must fit what the intake gave; cut or merge modules rather than squeezing.\n5. **Write it as `course.json`** in the shape in `references\u002Falignment.md`, then run:\n\n       python scripts\u002Fcheck_course.py course.json\n\n   It fails on an outcome nobody teaches or assesses, a prerequisite on a later or unknown\n   module, and a plan over its hour budget; it warns on unmeasurable outcome verbs, modules with\n   no outcome or no assessment, and modules over a quarter of the budget. Fix every FAIL.\n6. **Render the syllabus** for learners from the checked JSON: outcomes, the module table\n   (title, what you will be able to do, hours, assessment), how grading works and the rubric.\n\n## Rules\n\n- **Outcomes first, content second.** A topic that serves no outcome is cut or marked optional.\n- **One assessment per outcome, at least.** Final projects may assess several; say which.\n- **Rubrics describe evidence.** Each level says what the work shows, not \"good\" or \"excellent\".\n- **No invented resources.** Do not cite a book, course, dataset or tool you are not confident\n  exists; mark anything not checked this session `[unverified]`.\n- **Respect the learners' time.** Between-session work is counted in the budget, not hidden.\n\n## Handoffs\n\n| Signal | Owner | What you send |\n| --- | --- | --- |\n| One learner's own plan, practice routine, revision schedule | `study-system` | the outcomes, restated as that learner's target skill |\n| The concepts of one module need explaining | `topic-primer` | the module's outcome and the learners' starting level |\n| Handout, slide or announcement copy | `wordsmith` | the syllabus and the voice wanted |\n| Selling the course or cohort | `sales-copy` | the outcomes and who the course is for |\n| Course pages or a policy for refunds | `paper-trail` | the price, refund window and what learners submit |\n\n## Report\n\nLead with the outcomes and the checker result. Then the module table, total hours against the\nbudget, any WARN kept and why, assumptions made at intake, and the one next action.\n`references\u002Ftrigger-cases.md` holds the hand-run trigger cases; open it when tuning this\ndescription.\n",{"name":5,"version":24,"description":7},"1.0.0","main","523bc2bf98727c9fd981424f86ecba66c6d6ecd6","plugins\u002Fcaffeinity\u002Fskills\u002Fcourse-builder","https:\u002F\u002Fgithub.com\u002Farm-pz\u002Fcaffeinity-skills","https:\u002F\u002Fskills.caffeinity.com\u002F","https:\u002F\u002Fgithub.com\u002Farm-pz","skills.caffeinity.com","2026-11-14 01:22:10",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add arm-pz\u002Fcaffeinity-skills --skill course-builder",{"tool":39,"command":40},"bunx","bunx skills add arm-pz\u002Fcaffeinity-skills --skill course-builder",{"tool":42,"command":43},"pnpm","pnpm dlx skills add arm-pz\u002Fcaffeinity-skills --skill course-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farm-pz\u002Fcaffeinity-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcaffeinity\u002Fskills\u002Fcourse-builder\u002FSKILL.md",true,[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Falignment.md","REFERENCE","参考文档",2433,"https:\u002F\u002Fgithub.com\u002Farm-pz\u002Fcaffeinity-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcaffeinity\u002Fskills\u002Fcourse-builder\u002Freferences\u002Falignment.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Foutcomes.md",1458,"https:\u002F\u002Fgithub.com\u002Farm-pz\u002Fcaffeinity-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcaffeinity\u002Fskills\u002Fcourse-builder\u002Freferences\u002Foutcomes.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Ftrigger-cases.md",1790,"https:\u002F\u002Fgithub.com\u002Farm-pz\u002Fcaffeinity-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcaffeinity\u002Fskills\u002Fcourse-builder\u002Freferences\u002Ftrigger-cases.md",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"scripts\u002Fcheck_course.py","SCRIPT","脚本",4527,"https:\u002F\u002Fgithub.com\u002Farm-pz\u002Fcaffeinity-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcaffeinity\u002Fskills\u002Fcourse-builder\u002Fscripts\u002Fcheck_course.py",[68,75,82,89,94,101],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7EJR8K8FDPBY02RFPRRW19M","tune-and-ship","Takes one published skill at a time from as-is to tuned, fact-checked, released and live, then moves to the next one in the catalog. Each run tunes the skill with tune-skill, checks every version number, flag, price and command it states against the primary source, re-reads its siblings' real SKILL.md files, polishes the listing with findable-polish, writes the version and release notes, opens one PR, and after the merge confirms the site page and marketplace copy are live. Use whenever the user wants to fine-tune their other skills, work through the catalog, give a published skill the full treatment, fact-check a skill's claims, or ship a tune instead of drafting it, even if they never say \"ship\". Not for a tune with no release (use tune-skill), drafts with nothing pushed (use tune-and-polish), a new skill (use skill-launch), regressions from the nightly health check (use caffeinity-routing's Descale brew), or a whole collection (use skill-estate).","https:\u002F\u002Fgithub.com\u002Farm-pz\u002Fcaffeinity-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftune-and-ship\u002Fskills\u002Ftune-and-ship\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7EJR2D3H3EA8PT9PVR8DVTS","skill-estate","Takes a whole collection of agent skill repos from scattered to published, consistent and self-maintaining, in gated phases: inventory every repo, reconcile site, marketplace and README listings, test and tune the family, close workflow gaps, wire publishing so new skill repos go live on their own, bundle a plugin with agents, add trigger tests and directory listings, and leave a maintenance loop and a map. Each phase hands off to the skill that owns it and ends in PRs. Use when someone's skills site and GitHub disagree, wants all their skill repos audited or cleaned up, wants new skills to publish themselves, or wants that cleanup repeated on another org, even if they never say estate. Not for one skill (use tune-skill), one listing (use findable), the site pipeline alone (use publish-pipeline), or weekly upkeep (use caffeinity-routing's Descale brew).","https:\u002F\u002Fgithub.com\u002Farm-pz\u002Fcaffeinity-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskill-estate\u002Fskills\u002Fskill-estate\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7EJQVD17QR594SGFS5Z1T34","paper-trail","Drafts the policy pages a small product needs before it takes money or data (privacy policy, terms of service, refund policy, cookie notice) from a fact sheet about what the product actually collects, stores, shares and charges, then checks the drafts for placeholders, missing sections and facts nobody supplied. Use when someone needs a privacy policy, terms, refund or cookie page for a site, app, SaaS, newsletter or digital product, asks what legal pages they need before launch, or wants existing policy pages checked against what the product really does, even if they never say \"legal\". Not legal advice and not for contracts, NDAs or employment documents (use a lawyer), and not for the launch plan itself (use solo-income-blueprint) or the site build (use site-prompt).","https:\u002F\u002Fgithub.com\u002Farm-pz\u002Fcaffeinity-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpaper-trail\u002Fskills\u002Fpaper-trail\u002FSKILL.md",[],[],{"skillNo":90,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7EJQM55D4W6D9SJB8WDVP27","https:\u002F\u002Fgithub.com\u002Farm-pz\u002Fcaffeinity-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcourse-builder\u002Fskills\u002Fcourse-builder\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7EJQDFT8K0PW1HF7RPS6M03","wordsmith","Write, draft, rewrite, edit, proofread, polish and improve text while preserving the author's intended meaning, facts and voice. Use when the user wants clearer, shorter or better-toned writing; grammar, structure or flow fixes; emails, website or marketing copy, headlines, outlines or summaries; a different reading level; an accessibility, inclusivity or accuracy review; or content prepared for publication, even if they never say \"edit\". Also handles \u002Fwordsmith commands such as draft, critique, audit, tighten, tone and final. Not for resumes, CVs or LinkedIn profiles (use recruiter-lens if installed), not for code or code comments, and not for building .docx or .pdf files (write the text here, then use the file skill).","https:\u002F\u002Fgithub.com\u002Farm-pz\u002Fcaffeinity-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcaffeinity\u002Fskills\u002Fwordsmith\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7EJQ3TFWMSW96T0E49W310A","web-preflight","Use when shipping, deploying, publishing, launching, reviewing, or pre-flighting a website or API and you want a lightweight check for accidental exposure of secrets, source or configuration files, admin and debug surfaces, unsafe redirects, missing security controls, and misleading 200 responses. Trigger phrases include \"before we ship\", \"security check\", \"preflight\", \"audit the site\", \"check the production URL\", \"is my .env exposed\", and \"why does \u002F.env return 200\", including when access-log or analytics evidence is supplied. Checks only sites the user owns or is authorized to assess, with bounded GET and HEAD requests and a fixed compact path set; distinguishes genuine resources from SPA catch-all and blanket WAF responses. Not for penetration testing, exploitation, credential testing, broad port scanning, or application-code review; use a dedicated authorized security-testing or code-review workflow instead.","https:\u002F\u002Fgithub.com\u002Farm-pz\u002Fcaffeinity-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcaffeinity\u002Fskills\u002Fweb-preflight\u002FSKILL.md",[],[]]