[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-trail-of-bits-teach":3,"mdc--jrwv5r-key":34,"related-org-trail-of-bits-teach":749,"related-repo-trail-of-bits-teach":911},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":29,"sourceUrl":32,"mdContent":33},"teach","teach concepts through stateful sessions","Teaches the user a new skill or concept over multiple sessions, using the current directory as a stateful teaching workspace with lessons, learning records, and reference materials.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"trail-of-bits","Trail of Bits","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Ftrail-of-bits.png","trailofbits",[13,17,20],{"name":14,"slug":15,"type":16},"Knowledge Management","knowledge-management","tag",{"name":18,"slug":19,"type":16},"Education","education",{"name":21,"slug":22,"type":16},"Coaching","coaching",460,"https:\u002F\u002Fgithub.com\u002Ftrailofbits\u002Fskills-curated","2026-07-18T05:47:14.10436",null,29,[],{"repoUrl":24,"stars":23,"forks":27,"topics":30,"description":31},[],"Curated, community-vetted Claude Code plugin marketplace","https:\u002F\u002Fgithub.com\u002Ftrailofbits\u002Fskills-curated\u002Ftree\u002FHEAD\u002Fplugins\u002Fproductivity\u002Fskills\u002Fteach","---\nname: teach\ndescription: >-\n  Teaches the user a new skill or concept over multiple sessions, using the\n  current directory as a stateful teaching workspace with lessons, learning\n  records, and reference materials.\ndisable-model-invocation: true\nargument-hint: \"What would you like to learn about?\"\nallowed-tools:\n  - Read\n  - Write\n  - Edit\n  - Grep\n  - Glob\n  - Bash\n  - WebFetch\n  - WebSearch\n  - AskUserQuestion\n---\n\n# Teach\n\nThe user has asked you to teach them something. This is a stateful request —\nthey intend to learn the topic over multiple sessions.\n\n## When to Use\n\n- The user wants to learn a topic in depth over multiple sessions (a\n  programming language, a physical skill, a body of theory)\n- Returning to an existing teaching workspace to continue where a previous\n  session left off\n\n## When NOT to Use\n\n- The user asks a one-off question — just answer it; a workspace and learning\n  records are overhead with no payoff\n- The user wants a document or summary written for them rather than to learn\n  the material themselves\n\n## Teaching Workspace\n\nTreat the current directory as a teaching workspace. The state of their learning is captured in this directory in several files:\n\n- `MISSION.md`: A document capturing the _reason_ the user is interested in the topic. This should be used to ground all teaching. Use the format in [MISSION-FORMAT.md]({baseDir}\u002Freferences\u002FMISSION-FORMAT.md).\n- `.\u002Freference\u002F*.html`: A directory of reference materials. These are the compressed learnings from the lessons - cheat sheets, reference algorithms, syntax, yoga poses, glossaries. They are the raw units of learning. They should be beautiful documents which print out well, and are designed for quick reference.\n- `RESOURCES.md`: A list of resources which can be explored to ground your teaching in contextual knowledge, or to acquire knowledge and wisdom. Use the format in [RESOURCES-FORMAT.md]({baseDir}\u002Freferences\u002FRESOURCES-FORMAT.md).\n- `.\u002Flearning-records\u002F*.md`: A directory of learning records, which capture what the user has learned. These are loosely equivalent to architectural decision records in software development - they capture non-obvious lessons and key insights that may need to be revised later, or drive future sessions. These should be used to calculate the zone of proximal development. They are titled `0001-\u003Cdash-case-name>.md`, where the number increments each time. Use the format in [LEARNING-RECORD-FORMAT.md]({baseDir}\u002Freferences\u002FLEARNING-RECORD-FORMAT.md).\n- `.\u002Flessons\u002F*.html`: A directory of lessons. A **lesson** is a single, self-contained HTML output that teaches one tightly-scoped thing tied to the mission. This is the primary unit of teaching in this workspace.\n- `.\u002Fassets\u002F*`: Reusable **components** shared across lessons. See [Assets](#assets).\n- `NOTES.md`: A scratchpad for you to jot down user preferences, or working notes.\n\n## Philosophy\n\nTo learn at a deep level, the user needs three things:\n\n- **Knowledge**, captured from high-quality, high-trust resources\n- **Skills**, acquired through highly-relevant interactive lessons devised by you, based on the knowledge\n- **Wisdom**, which comes from interacting with other learners and practitioners\n\nBefore the `RESOURCES.md` is well-populated, your focus should be to find high-quality resources which will help the user acquire knowledge. Never trust your parametric knowledge.\n\nSome topics may require more skills than knowledge. Learning more about theoretical physics might be more knowledge-based. For yoga, more skills-based.\n\n### Fluency vs Storage Strength\n\nYou should be careful to split between two types of learning:\n\n- **Fluency strength**: in-the-moment retrieval of knowledge\n- **Storage strength**: long-term retention of knowledge\n\nFluency can give the user an illusory sense of mastery, but storage strength is the real goal. Try to design lessons which build long-term retention by desirable difficulty:\n\n- Using retrieval practice (recall from memory)\n- Spacing (distributing practice over time)\n- Interleaving (mixing up different but related topics in practice - for skills practice only)\n\n## Lessons\n\nA lesson is the main thing you produce — the unit in which knowledge and skills reach the user. Each lesson is one self-contained HTML file, saved to `.\u002Flessons\u002F` and titled `0001-\u003Cdash-case-name>.html` where the number increments each time.\n\nA lesson should be **beautiful** — clean, readable typography and layout — since the user will return to these later to review. Think Tufte.\n\nThe lesson should be short, and completable very quickly. Learners' working memory is very small, and we need to stay within it. But each lesson should give the user a single tangible win that they can build on. It should be directly tied to the mission, and should be in the user's zone of proximal development.\n\nIf possible, open the lesson file for the user by running a CLI command.\n\nEach lesson should link via HTML anchors to other lessons and reference documents.\n\nEach lesson should recommend a primary source for the user to read or watch. This should be the most high-quality, high-trust resource you found on the topic.\n\nEach lesson should contain a reminder to ask followup questions to the agent. The agent is their teacher, and can assist with anything that's unclear.\n\n## Assets\n\nLessons are built from reusable **components**, stored in `.\u002Fassets\u002F`: stylesheets, quiz widgets, simulators, diagram helpers — anything a second lesson could reuse.\n\nReuse is the default, not the exception. Before authoring a lesson, read `.\u002Fassets\u002F` and build from the components already there. When a lesson needs something new and reusable, write it as a component in `.\u002Fassets\u002F` and link to it — never inline code a future lesson would duplicate.\n\nA shared stylesheet is the first component every workspace earns: every lesson links it, so the lessons look like one consistent course rather than a pile of one-offs. As the workspace grows, so should the component library.\n\n## The Mission\n\nEvery lesson should be tied into the mission - the reason that the user is interested in learning about the topic.\n\nIf the user is unclear about the mission, or the `MISSION.md` is not populated, your first job should be to question the user on why they want to learn this.\n\nFailing to understand the mission will mean knowledge acquisition is not grounded in real-world goals. Lessons will feel too abstract. You will have no way of judging what the user should do next.\n\nMissions may change as the user develops more skills and knowledge. This is normal - make sure to update the `MISSION.md` and add a learning record to capture the change. Confirm with the user before changing the mission.\n\n## Zone Of Proximal Development\n\nEach lesson, the user should always feel as if they are being challenged 'just enough'.\n\nThe user may specify an exact thing they want to learn. If they don't, figure out their zone of proximal development by:\n\n- Reading their `learning-records`\n- Figuring out the right thing to teach them based on their mission\n- Teach the most relevant thing that fits in their zone of proximal development\n\n## Knowledge\n\nLessons should be designed around a skill the user is going to learn. The knowledge in the lesson should be only what's required to acquire that skill. You teach the knowledge first, then get the user to practice the skills via an interactive feedback loop.\n\nKnowledge should first be gathered from trusted resources. Use `RESOURCES.md` to keep track of them. Lessons should be littered with citations - links to external resources to back up any claim made. This increases the trustworthiness of the lesson.\n\nFor acquiring knowledge, difficulty is the enemy. It eats working memory you need for understanding.\n\n## Skills\n\nIf knowledge is all about acquisition, skills are about durability and flexibility. Make the knowledge stick.\n\nFor skill acquisition, difficulty is the tool. Effortful retrieval is what builds storage strength. Skills should be taught through interactive lessons. There are several tools at your disposal:\n\n- Interactive lessons, using quizzes and light in-browser tasks\n- Lessons which guide the user through a list of real-world steps to take (for instance, yoga poses)\n\nEach of these should be based on a **feedback loop**, where the user receives feedback on their performance. This feedback loop should be as tight as possible, giving feedback immediately - and ideally automatically.\n\nFor quizzes, each answer should be exactly the same number of words (and characters, if possible). Don't give the user any clues about the answer through formatting.\n\n## Acquiring Wisdom\n\nWisdom comes from true real-world interaction - testing your skills outside the learning environment.\n\nWhen the user asks a question that appears to require wisdom, your default posture should be to attempt to answer - but to ultimately delegate to a **community**.\n\nA community is a place (online or offline) where the user can test their skills in the real world. This might be a forum, a subreddit, a real-world class (budget permitting) or a local interest group.\n\nYou should attempt to find high-reputation communities the user can join. If the user expresses a preference that they don't want to join a community, respect it.\n\n## Reference Documents\n\nWhile creating lessons, you should also create reference documents. Lessons can reference these documents - they are useful for tracking raw units of knowledge useful across lessons.\n\nLessons will rarely be revisited later - reference documents will be. They should be the compressed essence of the lesson, in a format designed for quick reference.\n\nSome learning topics lend themselves to reference:\n\n- Syntax and code snippets for programming\n- Algorithms and flowcharts for processes\n- Yoga poses and sequences for yoga\n- Exercises and routines for fitness\n- Glossaries for any topic with its own nomenclature\n\nGlossaries, in particular, are an essential reference. Once one is created, it should be adhered to in every lesson. Use the format in [GLOSSARY-FORMAT.md]({baseDir}\u002Freferences\u002FGLOSSARY-FORMAT.md).\n\n## `NOTES.md`\n\nThe user will sometimes express preferences of how they want to be taught, or things you should keep in mind. This is the place to record those preferences, so you can refer back to them when designing lessons or working with the user.\n",{"data":35,"body":48},{"name":4,"description":6,"disable-model-invocation":36,"argument-hint":37,"allowed-tools":38},true,"What would you like to learn about?",[39,40,41,42,43,44,45,46,47],"Read","Write","Edit","Grep","Glob","Bash","WebFetch","WebSearch","AskUserQuestion",{"type":49,"children":50},"root",[51,59,65,72,87,93,106,112,117,259,265,270,303,315,320,327,332,355,360,378,384,405,417,422,427,432,437,442,447,466,485,490,496,501,513,518,530,536,541,546,570,575,580,592,597,602,607,612,625,637,642,648,653,664,669,674,680,685,690,695,723,735,744],{"type":52,"tag":53,"props":54,"children":55},"element","h1",{"id":4},[56],{"type":57,"value":58},"text","Teach",{"type":52,"tag":60,"props":61,"children":62},"p",{},[63],{"type":57,"value":64},"The user has asked you to teach them something. This is a stateful request —\nthey intend to learn the topic over multiple sessions.",{"type":52,"tag":66,"props":67,"children":69},"h2",{"id":68},"when-to-use",[70],{"type":57,"value":71},"When to Use",{"type":52,"tag":73,"props":74,"children":75},"ul",{},[76,82],{"type":52,"tag":77,"props":78,"children":79},"li",{},[80],{"type":57,"value":81},"The user wants to learn a topic in depth over multiple sessions (a\nprogramming language, a physical skill, a body of theory)",{"type":52,"tag":77,"props":83,"children":84},{},[85],{"type":57,"value":86},"Returning to an existing teaching workspace to continue where a previous\nsession left off",{"type":52,"tag":66,"props":88,"children":90},{"id":89},"when-not-to-use",[91],{"type":57,"value":92},"When NOT to Use",{"type":52,"tag":73,"props":94,"children":95},{},[96,101],{"type":52,"tag":77,"props":97,"children":98},{},[99],{"type":57,"value":100},"The user asks a one-off question — just answer it; a workspace and learning\nrecords are overhead with no payoff",{"type":52,"tag":77,"props":102,"children":103},{},[104],{"type":57,"value":105},"The user wants a document or summary written for them rather than to learn\nthe material themselves",{"type":52,"tag":66,"props":107,"children":109},{"id":108},"teaching-workspace",[110],{"type":57,"value":111},"Teaching Workspace",{"type":52,"tag":60,"props":113,"children":114},{},[115],{"type":57,"value":116},"Treat the current directory as a teaching workspace. The state of their learning is captured in this directory in several files:",{"type":52,"tag":73,"props":118,"children":119},{},[120,149,160,178,204,223,248],{"type":52,"tag":77,"props":121,"children":122},{},[123,130,132,138,140,147],{"type":52,"tag":124,"props":125,"children":127},"code",{"className":126},[],[128],{"type":57,"value":129},"MISSION.md",{"type":57,"value":131},": A document capturing the ",{"type":52,"tag":133,"props":134,"children":135},"em",{},[136],{"type":57,"value":137},"reason",{"type":57,"value":139}," the user is interested in the topic. This should be used to ground all teaching. Use the format in ",{"type":52,"tag":141,"props":142,"children":144},"a",{"href":143},"%7BbaseDir%7D\u002Freferences\u002FMISSION-FORMAT.md",[145],{"type":57,"value":146},"MISSION-FORMAT.md",{"type":57,"value":148},".",{"type":52,"tag":77,"props":150,"children":151},{},[152,158],{"type":52,"tag":124,"props":153,"children":155},{"className":154},[],[156],{"type":57,"value":157},".\u002Freference\u002F*.html",{"type":57,"value":159},": A directory of reference materials. These are the compressed learnings from the lessons - cheat sheets, reference algorithms, syntax, yoga poses, glossaries. They are the raw units of learning. They should be beautiful documents which print out well, and are designed for quick reference.",{"type":52,"tag":77,"props":161,"children":162},{},[163,169,171,177],{"type":52,"tag":124,"props":164,"children":166},{"className":165},[],[167],{"type":57,"value":168},"RESOURCES.md",{"type":57,"value":170},": A list of resources which can be explored to ground your teaching in contextual knowledge, or to acquire knowledge and wisdom. Use the format in ",{"type":52,"tag":141,"props":172,"children":174},{"href":173},"%7BbaseDir%7D\u002Freferences\u002FRESOURCES-FORMAT.md",[175],{"type":57,"value":176},"RESOURCES-FORMAT.md",{"type":57,"value":148},{"type":52,"tag":77,"props":179,"children":180},{},[181,187,189,195,197,203],{"type":52,"tag":124,"props":182,"children":184},{"className":183},[],[185],{"type":57,"value":186},".\u002Flearning-records\u002F*.md",{"type":57,"value":188},": A directory of learning records, which capture what the user has learned. These are loosely equivalent to architectural decision records in software development - they capture non-obvious lessons and key insights that may need to be revised later, or drive future sessions. These should be used to calculate the zone of proximal development. They are titled ",{"type":52,"tag":124,"props":190,"children":192},{"className":191},[],[193],{"type":57,"value":194},"0001-\u003Cdash-case-name>.md",{"type":57,"value":196},", where the number increments each time. Use the format in ",{"type":52,"tag":141,"props":198,"children":200},{"href":199},"%7BbaseDir%7D\u002Freferences\u002FLEARNING-RECORD-FORMAT.md",[201],{"type":57,"value":202},"LEARNING-RECORD-FORMAT.md",{"type":57,"value":148},{"type":52,"tag":77,"props":205,"children":206},{},[207,213,215,221],{"type":52,"tag":124,"props":208,"children":210},{"className":209},[],[211],{"type":57,"value":212},".\u002Flessons\u002F*.html",{"type":57,"value":214},": A directory of lessons. A ",{"type":52,"tag":216,"props":217,"children":218},"strong",{},[219],{"type":57,"value":220},"lesson",{"type":57,"value":222}," is a single, self-contained HTML output that teaches one tightly-scoped thing tied to the mission. This is the primary unit of teaching in this workspace.",{"type":52,"tag":77,"props":224,"children":225},{},[226,232,234,239,241,247],{"type":52,"tag":124,"props":227,"children":229},{"className":228},[],[230],{"type":57,"value":231},".\u002Fassets\u002F*",{"type":57,"value":233},": Reusable ",{"type":52,"tag":216,"props":235,"children":236},{},[237],{"type":57,"value":238},"components",{"type":57,"value":240}," shared across lessons. See ",{"type":52,"tag":141,"props":242,"children":244},{"href":243},"#assets",[245],{"type":57,"value":246},"Assets",{"type":57,"value":148},{"type":52,"tag":77,"props":249,"children":250},{},[251,257],{"type":52,"tag":124,"props":252,"children":254},{"className":253},[],[255],{"type":57,"value":256},"NOTES.md",{"type":57,"value":258},": A scratchpad for you to jot down user preferences, or working notes.",{"type":52,"tag":66,"props":260,"children":262},{"id":261},"philosophy",[263],{"type":57,"value":264},"Philosophy",{"type":52,"tag":60,"props":266,"children":267},{},[268],{"type":57,"value":269},"To learn at a deep level, the user needs three things:",{"type":52,"tag":73,"props":271,"children":272},{},[273,283,293],{"type":52,"tag":77,"props":274,"children":275},{},[276,281],{"type":52,"tag":216,"props":277,"children":278},{},[279],{"type":57,"value":280},"Knowledge",{"type":57,"value":282},", captured from high-quality, high-trust resources",{"type":52,"tag":77,"props":284,"children":285},{},[286,291],{"type":52,"tag":216,"props":287,"children":288},{},[289],{"type":57,"value":290},"Skills",{"type":57,"value":292},", acquired through highly-relevant interactive lessons devised by you, based on the knowledge",{"type":52,"tag":77,"props":294,"children":295},{},[296,301],{"type":52,"tag":216,"props":297,"children":298},{},[299],{"type":57,"value":300},"Wisdom",{"type":57,"value":302},", which comes from interacting with other learners and practitioners",{"type":52,"tag":60,"props":304,"children":305},{},[306,308,313],{"type":57,"value":307},"Before the ",{"type":52,"tag":124,"props":309,"children":311},{"className":310},[],[312],{"type":57,"value":168},{"type":57,"value":314}," is well-populated, your focus should be to find high-quality resources which will help the user acquire knowledge. Never trust your parametric knowledge.",{"type":52,"tag":60,"props":316,"children":317},{},[318],{"type":57,"value":319},"Some topics may require more skills than knowledge. Learning more about theoretical physics might be more knowledge-based. For yoga, more skills-based.",{"type":52,"tag":321,"props":322,"children":324},"h3",{"id":323},"fluency-vs-storage-strength",[325],{"type":57,"value":326},"Fluency vs Storage Strength",{"type":52,"tag":60,"props":328,"children":329},{},[330],{"type":57,"value":331},"You should be careful to split between two types of learning:",{"type":52,"tag":73,"props":333,"children":334},{},[335,345],{"type":52,"tag":77,"props":336,"children":337},{},[338,343],{"type":52,"tag":216,"props":339,"children":340},{},[341],{"type":57,"value":342},"Fluency strength",{"type":57,"value":344},": in-the-moment retrieval of knowledge",{"type":52,"tag":77,"props":346,"children":347},{},[348,353],{"type":52,"tag":216,"props":349,"children":350},{},[351],{"type":57,"value":352},"Storage strength",{"type":57,"value":354},": long-term retention of knowledge",{"type":52,"tag":60,"props":356,"children":357},{},[358],{"type":57,"value":359},"Fluency can give the user an illusory sense of mastery, but storage strength is the real goal. Try to design lessons which build long-term retention by desirable difficulty:",{"type":52,"tag":73,"props":361,"children":362},{},[363,368,373],{"type":52,"tag":77,"props":364,"children":365},{},[366],{"type":57,"value":367},"Using retrieval practice (recall from memory)",{"type":52,"tag":77,"props":369,"children":370},{},[371],{"type":57,"value":372},"Spacing (distributing practice over time)",{"type":52,"tag":77,"props":374,"children":375},{},[376],{"type":57,"value":377},"Interleaving (mixing up different but related topics in practice - for skills practice only)",{"type":52,"tag":66,"props":379,"children":381},{"id":380},"lessons",[382],{"type":57,"value":383},"Lessons",{"type":52,"tag":60,"props":385,"children":386},{},[387,389,395,397,403],{"type":57,"value":388},"A lesson is the main thing you produce — the unit in which knowledge and skills reach the user. Each lesson is one self-contained HTML file, saved to ",{"type":52,"tag":124,"props":390,"children":392},{"className":391},[],[393],{"type":57,"value":394},".\u002Flessons\u002F",{"type":57,"value":396}," and titled ",{"type":52,"tag":124,"props":398,"children":400},{"className":399},[],[401],{"type":57,"value":402},"0001-\u003Cdash-case-name>.html",{"type":57,"value":404}," where the number increments each time.",{"type":52,"tag":60,"props":406,"children":407},{},[408,410,415],{"type":57,"value":409},"A lesson should be ",{"type":52,"tag":216,"props":411,"children":412},{},[413],{"type":57,"value":414},"beautiful",{"type":57,"value":416}," — clean, readable typography and layout — since the user will return to these later to review. Think Tufte.",{"type":52,"tag":60,"props":418,"children":419},{},[420],{"type":57,"value":421},"The lesson should be short, and completable very quickly. Learners' working memory is very small, and we need to stay within it. But each lesson should give the user a single tangible win that they can build on. It should be directly tied to the mission, and should be in the user's zone of proximal development.",{"type":52,"tag":60,"props":423,"children":424},{},[425],{"type":57,"value":426},"If possible, open the lesson file for the user by running a CLI command.",{"type":52,"tag":60,"props":428,"children":429},{},[430],{"type":57,"value":431},"Each lesson should link via HTML anchors to other lessons and reference documents.",{"type":52,"tag":60,"props":433,"children":434},{},[435],{"type":57,"value":436},"Each lesson should recommend a primary source for the user to read or watch. This should be the most high-quality, high-trust resource you found on the topic.",{"type":52,"tag":60,"props":438,"children":439},{},[440],{"type":57,"value":441},"Each lesson should contain a reminder to ask followup questions to the agent. The agent is their teacher, and can assist with anything that's unclear.",{"type":52,"tag":66,"props":443,"children":445},{"id":444},"assets",[446],{"type":57,"value":246},{"type":52,"tag":60,"props":448,"children":449},{},[450,452,456,458,464],{"type":57,"value":451},"Lessons are built from reusable ",{"type":52,"tag":216,"props":453,"children":454},{},[455],{"type":57,"value":238},{"type":57,"value":457},", stored in ",{"type":52,"tag":124,"props":459,"children":461},{"className":460},[],[462],{"type":57,"value":463},".\u002Fassets\u002F",{"type":57,"value":465},": stylesheets, quiz widgets, simulators, diagram helpers — anything a second lesson could reuse.",{"type":52,"tag":60,"props":467,"children":468},{},[469,471,476,478,483],{"type":57,"value":470},"Reuse is the default, not the exception. Before authoring a lesson, read ",{"type":52,"tag":124,"props":472,"children":474},{"className":473},[],[475],{"type":57,"value":463},{"type":57,"value":477}," and build from the components already there. When a lesson needs something new and reusable, write it as a component in ",{"type":52,"tag":124,"props":479,"children":481},{"className":480},[],[482],{"type":57,"value":463},{"type":57,"value":484}," and link to it — never inline code a future lesson would duplicate.",{"type":52,"tag":60,"props":486,"children":487},{},[488],{"type":57,"value":489},"A shared stylesheet is the first component every workspace earns: every lesson links it, so the lessons look like one consistent course rather than a pile of one-offs. As the workspace grows, so should the component library.",{"type":52,"tag":66,"props":491,"children":493},{"id":492},"the-mission",[494],{"type":57,"value":495},"The Mission",{"type":52,"tag":60,"props":497,"children":498},{},[499],{"type":57,"value":500},"Every lesson should be tied into the mission - the reason that the user is interested in learning about the topic.",{"type":52,"tag":60,"props":502,"children":503},{},[504,506,511],{"type":57,"value":505},"If the user is unclear about the mission, or the ",{"type":52,"tag":124,"props":507,"children":509},{"className":508},[],[510],{"type":57,"value":129},{"type":57,"value":512}," is not populated, your first job should be to question the user on why they want to learn this.",{"type":52,"tag":60,"props":514,"children":515},{},[516],{"type":57,"value":517},"Failing to understand the mission will mean knowledge acquisition is not grounded in real-world goals. Lessons will feel too abstract. You will have no way of judging what the user should do next.",{"type":52,"tag":60,"props":519,"children":520},{},[521,523,528],{"type":57,"value":522},"Missions may change as the user develops more skills and knowledge. This is normal - make sure to update the ",{"type":52,"tag":124,"props":524,"children":526},{"className":525},[],[527],{"type":57,"value":129},{"type":57,"value":529}," and add a learning record to capture the change. Confirm with the user before changing the mission.",{"type":52,"tag":66,"props":531,"children":533},{"id":532},"zone-of-proximal-development",[534],{"type":57,"value":535},"Zone Of Proximal Development",{"type":52,"tag":60,"props":537,"children":538},{},[539],{"type":57,"value":540},"Each lesson, the user should always feel as if they are being challenged 'just enough'.",{"type":52,"tag":60,"props":542,"children":543},{},[544],{"type":57,"value":545},"The user may specify an exact thing they want to learn. If they don't, figure out their zone of proximal development by:",{"type":52,"tag":73,"props":547,"children":548},{},[549,560,565],{"type":52,"tag":77,"props":550,"children":551},{},[552,554],{"type":57,"value":553},"Reading their ",{"type":52,"tag":124,"props":555,"children":557},{"className":556},[],[558],{"type":57,"value":559},"learning-records",{"type":52,"tag":77,"props":561,"children":562},{},[563],{"type":57,"value":564},"Figuring out the right thing to teach them based on their mission",{"type":52,"tag":77,"props":566,"children":567},{},[568],{"type":57,"value":569},"Teach the most relevant thing that fits in their zone of proximal development",{"type":52,"tag":66,"props":571,"children":573},{"id":572},"knowledge",[574],{"type":57,"value":280},{"type":52,"tag":60,"props":576,"children":577},{},[578],{"type":57,"value":579},"Lessons should be designed around a skill the user is going to learn. The knowledge in the lesson should be only what's required to acquire that skill. You teach the knowledge first, then get the user to practice the skills via an interactive feedback loop.",{"type":52,"tag":60,"props":581,"children":582},{},[583,585,590],{"type":57,"value":584},"Knowledge should first be gathered from trusted resources. Use ",{"type":52,"tag":124,"props":586,"children":588},{"className":587},[],[589],{"type":57,"value":168},{"type":57,"value":591}," to keep track of them. Lessons should be littered with citations - links to external resources to back up any claim made. This increases the trustworthiness of the lesson.",{"type":52,"tag":60,"props":593,"children":594},{},[595],{"type":57,"value":596},"For acquiring knowledge, difficulty is the enemy. It eats working memory you need for understanding.",{"type":52,"tag":66,"props":598,"children":600},{"id":599},"skills",[601],{"type":57,"value":290},{"type":52,"tag":60,"props":603,"children":604},{},[605],{"type":57,"value":606},"If knowledge is all about acquisition, skills are about durability and flexibility. Make the knowledge stick.",{"type":52,"tag":60,"props":608,"children":609},{},[610],{"type":57,"value":611},"For skill acquisition, difficulty is the tool. Effortful retrieval is what builds storage strength. Skills should be taught through interactive lessons. There are several tools at your disposal:",{"type":52,"tag":73,"props":613,"children":614},{},[615,620],{"type":52,"tag":77,"props":616,"children":617},{},[618],{"type":57,"value":619},"Interactive lessons, using quizzes and light in-browser tasks",{"type":52,"tag":77,"props":621,"children":622},{},[623],{"type":57,"value":624},"Lessons which guide the user through a list of real-world steps to take (for instance, yoga poses)",{"type":52,"tag":60,"props":626,"children":627},{},[628,630,635],{"type":57,"value":629},"Each of these should be based on a ",{"type":52,"tag":216,"props":631,"children":632},{},[633],{"type":57,"value":634},"feedback loop",{"type":57,"value":636},", where the user receives feedback on their performance. This feedback loop should be as tight as possible, giving feedback immediately - and ideally automatically.",{"type":52,"tag":60,"props":638,"children":639},{},[640],{"type":57,"value":641},"For quizzes, each answer should be exactly the same number of words (and characters, if possible). Don't give the user any clues about the answer through formatting.",{"type":52,"tag":66,"props":643,"children":645},{"id":644},"acquiring-wisdom",[646],{"type":57,"value":647},"Acquiring Wisdom",{"type":52,"tag":60,"props":649,"children":650},{},[651],{"type":57,"value":652},"Wisdom comes from true real-world interaction - testing your skills outside the learning environment.",{"type":52,"tag":60,"props":654,"children":655},{},[656,658,663],{"type":57,"value":657},"When the user asks a question that appears to require wisdom, your default posture should be to attempt to answer - but to ultimately delegate to a ",{"type":52,"tag":216,"props":659,"children":660},{},[661],{"type":57,"value":662},"community",{"type":57,"value":148},{"type":52,"tag":60,"props":665,"children":666},{},[667],{"type":57,"value":668},"A community is a place (online or offline) where the user can test their skills in the real world. This might be a forum, a subreddit, a real-world class (budget permitting) or a local interest group.",{"type":52,"tag":60,"props":670,"children":671},{},[672],{"type":57,"value":673},"You should attempt to find high-reputation communities the user can join. If the user expresses a preference that they don't want to join a community, respect it.",{"type":52,"tag":66,"props":675,"children":677},{"id":676},"reference-documents",[678],{"type":57,"value":679},"Reference Documents",{"type":52,"tag":60,"props":681,"children":682},{},[683],{"type":57,"value":684},"While creating lessons, you should also create reference documents. Lessons can reference these documents - they are useful for tracking raw units of knowledge useful across lessons.",{"type":52,"tag":60,"props":686,"children":687},{},[688],{"type":57,"value":689},"Lessons will rarely be revisited later - reference documents will be. They should be the compressed essence of the lesson, in a format designed for quick reference.",{"type":52,"tag":60,"props":691,"children":692},{},[693],{"type":57,"value":694},"Some learning topics lend themselves to reference:",{"type":52,"tag":73,"props":696,"children":697},{},[698,703,708,713,718],{"type":52,"tag":77,"props":699,"children":700},{},[701],{"type":57,"value":702},"Syntax and code snippets for programming",{"type":52,"tag":77,"props":704,"children":705},{},[706],{"type":57,"value":707},"Algorithms and flowcharts for processes",{"type":52,"tag":77,"props":709,"children":710},{},[711],{"type":57,"value":712},"Yoga poses and sequences for yoga",{"type":52,"tag":77,"props":714,"children":715},{},[716],{"type":57,"value":717},"Exercises and routines for fitness",{"type":52,"tag":77,"props":719,"children":720},{},[721],{"type":57,"value":722},"Glossaries for any topic with its own nomenclature",{"type":52,"tag":60,"props":724,"children":725},{},[726,728,734],{"type":57,"value":727},"Glossaries, in particular, are an essential reference. Once one is created, it should be adhered to in every lesson. Use the format in ",{"type":52,"tag":141,"props":729,"children":731},{"href":730},"%7BbaseDir%7D\u002Freferences\u002FGLOSSARY-FORMAT.md",[732],{"type":57,"value":733},"GLOSSARY-FORMAT.md",{"type":57,"value":148},{"type":52,"tag":66,"props":736,"children":738},{"id":737},"notesmd",[739],{"type":52,"tag":124,"props":740,"children":742},{"className":741},[],[743],{"type":57,"value":256},{"type":52,"tag":60,"props":745,"children":746},{},[747],{"type":57,"value":748},"The user will sometimes express preferences of how they want to be taught, or things you should keep in mind. This is the place to record those preferences, so you can refer back to them when designing lessons or working with the user.",{"items":750,"total":910},[751,772,782,802,817,830,842,852,865,876,888,899],{"slug":752,"name":752,"fn":753,"description":754,"org":755,"tags":756,"stars":769,"repoUrl":770,"updatedAt":771},"address-sanitizer","detect memory errors during fuzzing","AddressSanitizer detects memory errors during fuzzing. Use when fuzzing C\u002FC++ code to find buffer overflows and use-after-free bugs.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[757,760,763,766],{"name":758,"slug":759,"type":16},"C#","c",{"name":761,"slug":762,"type":16},"Debugging","debugging",{"name":764,"slug":765,"type":16},"Security","security",{"name":767,"slug":768,"type":16},"Testing","testing",6139,"https:\u002F\u002Fgithub.com\u002Ftrailofbits\u002Fskills","2026-07-17T06:05:14.925095",{"slug":773,"name":773,"fn":774,"description":775,"org":776,"tags":777,"stars":769,"repoUrl":770,"updatedAt":781},"aflpp","perform multi-core fuzzing of C\u002FC++ projects","AFL++ is a fork of AFL with better fuzzing performance and advanced features. Use for multi-core fuzzing of C\u002FC++ projects.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[778,779,780],{"name":758,"slug":759,"type":16},{"name":764,"slug":765,"type":16},{"name":767,"slug":768,"type":16},"2026-07-17T06:05:12.433192",{"slug":783,"name":783,"fn":784,"description":785,"org":786,"tags":787,"stars":769,"repoUrl":770,"updatedAt":801},"agentic-actions-auditor","audit GitHub Actions for security vulnerabilities","Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches AI agents running in CI\u002FCD pipelines, including env var intermediary patterns, direct expression injection, dangerous sandbox configurations, and wildcard user allowlists. Use when reviewing workflow files that invoke AI coding agents, auditing CI\u002FCD pipeline security for prompt injection risks, or evaluating agentic action configurations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[788,791,794,797,800],{"name":789,"slug":790,"type":16},"Agents","agents",{"name":792,"slug":793,"type":16},"CI\u002FCD","ci-cd",{"name":795,"slug":796,"type":16},"Code Analysis","code-analysis",{"name":798,"slug":799,"type":16},"GitHub Actions","github-actions",{"name":764,"slug":765,"type":16},"2026-07-18T05:47:48.564744",{"slug":803,"name":803,"fn":804,"description":805,"org":806,"tags":807,"stars":769,"repoUrl":770,"updatedAt":816},"algorand-vulnerability-scanner","scan Algorand smart contracts for vulnerabilities","Scans Algorand smart contracts for 11 common vulnerabilities including rekeying attacks, unchecked transaction fees, missing field validations, and access control issues. Use when auditing Algorand projects (TEAL\u002FPyTeal).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[808,811,812,813],{"name":809,"slug":810,"type":16},"Audit","audit",{"name":795,"slug":796,"type":16},{"name":764,"slug":765,"type":16},{"name":814,"slug":815,"type":16},"Smart Contracts","smart-contracts","2026-07-18T05:47:43.989063",{"slug":818,"name":818,"fn":819,"description":820,"org":821,"tags":822,"stars":769,"repoUrl":770,"updatedAt":829},"ask-questions-if-underspecified","clarify requirements before implementation","Clarify requirements before implementing. Use when serious doubts arise.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[823,826],{"name":824,"slug":825,"type":16},"Engineering","engineering",{"name":827,"slug":828,"type":16},"Productivity","productivity","2026-07-17T06:05:33.543262",{"slug":831,"name":831,"fn":832,"description":833,"org":834,"tags":835,"stars":769,"repoUrl":770,"updatedAt":841},"atheris","fuzz Python code with Atheris","Atheris is a coverage-guided Python fuzzer based on libFuzzer. Use for fuzzing pure Python code and Python C extensions.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[836,839,840],{"name":837,"slug":838,"type":16},"Python","python",{"name":764,"slug":765,"type":16},{"name":767,"slug":768,"type":16},"2026-07-17T06:05:14.575191",{"slug":843,"name":843,"fn":844,"description":845,"org":846,"tags":847,"stars":769,"repoUrl":770,"updatedAt":851},"audit-augmentation","augment code graphs with audit findings","Augments Trailmark code graphs with external audit findings from SARIF static analysis results, weAudit annotation files, and version-gated Trailmark 0.4.x binary-analysis graph exports. Maps findings to graph nodes by file and line overlap, creates severity-based subgraphs, and enables cross-referencing findings with pre-analysis data (blast radius, taint, etc.). Use when projecting SARIF results onto a code graph, overlaying weAudit annotations, importing binary graph findings, cross-referencing Semgrep, CodeQL, or binary-analysis findings with call graph data, or visualizing audit findings in the context of code structure.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[848,849,850],{"name":809,"slug":810,"type":16},{"name":795,"slug":796,"type":16},{"name":764,"slug":765,"type":16},"2026-08-01T05:44:54.920542",{"slug":853,"name":853,"fn":854,"description":855,"org":856,"tags":857,"stars":769,"repoUrl":770,"updatedAt":864},"audit-context-building","build architectural context for code analysis","Enables ultra-granular, line-by-line code analysis to build deep architectural context before vulnerability or bug finding.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[858,861,862,863],{"name":859,"slug":860,"type":16},"Architecture","architecture",{"name":809,"slug":810,"type":16},{"name":795,"slug":796,"type":16},{"name":824,"slug":825,"type":16},"2026-07-18T05:47:40.122449",{"slug":866,"name":866,"fn":867,"description":868,"org":869,"tags":870,"stars":769,"repoUrl":770,"updatedAt":875},"audit-prep-assistant","prepare codebases for security audits","Prepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[871,872,873,874],{"name":809,"slug":810,"type":16},{"name":795,"slug":796,"type":16},{"name":824,"slug":825,"type":16},{"name":764,"slug":765,"type":16},"2026-07-18T05:47:39.210985",{"slug":877,"name":877,"fn":878,"description":879,"org":880,"tags":881,"stars":769,"repoUrl":770,"updatedAt":887},"burpsuite-project-parser","parse Burp Suite project files","Searches and explores Burp Suite project files (.burp) from the command line. Use when searching response headers or bodies with regex patterns, extracting security audit findings, dumping proxy history or site map data, or analyzing HTTP traffic captured in a Burp project.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[882,883,886],{"name":809,"slug":810,"type":16},{"name":884,"slug":885,"type":16},"CLI","cli",{"name":764,"slug":765,"type":16},"2026-07-17T06:05:33.198077",{"slug":889,"name":889,"fn":890,"description":891,"org":892,"tags":893,"stars":769,"repoUrl":770,"updatedAt":898},"c-review","audit C and C++ code","Performs comprehensive C\u002FC++ security review for memory corruption, integer overflows, race conditions, and platform-specific vulnerabilities. Use when auditing native C\u002FC++ applications, reviewing daemons or services for memory safety, or hunting integer overflow \u002F use-after-free \u002F race conditions in userspace code.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[894,895,896,897],{"name":809,"slug":810,"type":16},{"name":758,"slug":759,"type":16},{"name":795,"slug":796,"type":16},{"name":764,"slug":765,"type":16},"2026-07-17T06:05:11.333374",{"slug":900,"name":900,"fn":901,"description":902,"org":903,"tags":904,"stars":769,"repoUrl":770,"updatedAt":909},"cairo-vulnerability-scanner","scan Cairo and StarkNet contracts for vulnerabilities","Scans Cairo\u002FStarkNet smart contracts for 6 critical vulnerabilities including felt252 arithmetic overflow, L1-L2 messaging issues, address conversion problems, and signature replay. Use when auditing StarkNet projects.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[905,906,907,908],{"name":809,"slug":810,"type":16},{"name":795,"slug":796,"type":16},{"name":764,"slug":765,"type":16},{"name":814,"slug":815,"type":16},"2026-07-18T05:47:42.84568",111,{"items":912,"total":1011},[913,923,933,950,962,978,992],{"slug":914,"name":914,"fn":915,"description":916,"org":917,"tags":918,"stars":23,"repoUrl":24,"updatedAt":922},"ffuf-web-fuzzing","perform web fuzzing with ffuf","Expert guidance for ffuf web fuzzing during authorized penetration testing. Covers directory discovery, subdomain enumeration, parameter fuzzing, authenticated fuzzing with raw requests, auto-calibration, and result analysis. Use when running ffuf scans, analyzing ffuf output, or building fuzzing strategies for web targets.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[919,920,921],{"name":795,"slug":796,"type":16},{"name":764,"slug":765,"type":16},{"name":767,"slug":768,"type":16},"2026-07-17T06:05:08.247908",{"slug":924,"name":924,"fn":925,"description":926,"org":927,"tags":928,"stars":23,"repoUrl":24,"updatedAt":932},"ghidra-headless","reverse engineer binaries with Ghidra","Reverse engineers binaries using Ghidra's headless analyzer. Use when decompiling executables, extracting functions, strings, symbols, or analyzing call graphs from compiled binaries without the Ghidra GUI.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[929,930,931],{"name":795,"slug":796,"type":16},{"name":761,"slug":762,"type":16},{"name":764,"slug":765,"type":16},"2026-07-18T05:47:30.015093",{"slug":934,"name":934,"fn":935,"description":936,"org":937,"tags":938,"stars":23,"repoUrl":24,"updatedAt":949},"grilling","stress-test plans and decisions","Interviews the user relentlessly about a plan, decision, or idea until every branch of the decision tree is resolved. Use when the user wants to stress-test their thinking, sharpen a plan or design before acting, or uses any 'grill' trigger phrase (e.g. \"grill me on this\").",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[939,942,943,946],{"name":940,"slug":941,"type":16},"Analysis","analysis",{"name":21,"slug":22,"type":16},{"name":944,"slug":945,"type":16},"Ideation","ideation",{"name":947,"slug":948,"type":16},"Strategy","strategy","2026-07-18T05:48:12.46583",{"slug":951,"name":951,"fn":952,"description":953,"org":954,"tags":955,"stars":23,"repoUrl":24,"updatedAt":961},"handoff","compact conversation for session handoff","Compacts the current conversation into a handoff document so a fresh agent can continue the work in a new session.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[956,957,960],{"name":789,"slug":790,"type":16},{"name":958,"slug":959,"type":16},"Context","context",{"name":827,"slug":828,"type":16},"2026-07-18T05:47:03.196098",{"slug":963,"name":963,"fn":964,"description":965,"org":966,"tags":967,"stars":23,"repoUrl":24,"updatedAt":977},"humanizer","edit text to sound human-written","Remove signs of AI-generated writing from text. Use when editing or reviewing\ntext to make it sound more natural and human-written. Based on Wikipedia's\ncomprehensive \"Signs of AI writing\" guide. Detects and fixes patterns including:\ninflated symbolism, promotional language, superficial -ing analyses, vague\nattributions, em dash overuse, rule of three, AI vocabulary words, negative\nparallelisms, and excessive conjunctive phrases. 30c5c8d (Update humanizer plugin to upstream v2.2.0)\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[968,971,974],{"name":969,"slug":970,"type":16},"Content Creation","content-creation",{"name":972,"slug":973,"type":16},"Editing","editing",{"name":975,"slug":976,"type":16},"Writing","writing","2026-07-18T05:47:18.1749",{"slug":979,"name":979,"fn":980,"description":981,"org":982,"tags":983,"stars":23,"repoUrl":24,"updatedAt":991},"last30days","research recent community discussions and trends","Researches a topic from the last 30 days on Reddit, X, and the web. Surfaces real community discussions with engagement metrics and synthesizes findings into actionable insights. Use when the user wants to know what people are saying about a topic right now.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[984,985,988],{"name":940,"slug":941,"type":16},{"name":986,"slug":987,"type":16},"Research","research",{"name":989,"slug":990,"type":16},"Social Media","social-media","2026-07-17T06:04:39.744471",{"slug":993,"name":993,"fn":994,"description":995,"org":996,"tags":997,"stars":23,"repoUrl":24,"updatedAt":1010},"openai-cloudflare-deploy","deploy applications to Cloudflare","Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare. Originally from OpenAI's curated skills catalog.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[998,1001,1004,1007],{"name":999,"slug":1000,"type":16},"Cloudflare","cloudflare",{"name":1002,"slug":1003,"type":16},"Cloudflare Pages","cloudflare-pages",{"name":1005,"slug":1006,"type":16},"Cloudflare Workers","cloudflare-workers",{"name":1008,"slug":1009,"type":16},"Deployment","deployment","2026-07-17T06:04:46.574433",31]