[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A0205TJ1HA9SYRDTJX40JB":3,"skill-same:01M7A0205TJ1HA9SYRDTJX40JB":48},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7A0205TJ1HA9SYRDTJX40JB","Teach From Sources",null,"Read the links or sources the user gives, in the workspace browser, and teach the topic from them — grounded, ordered, and honest about what the sources do not say.","juspay\u002Fxyne-spaces","juspay","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11497632?v=4","01M79ZZZBS47MDBJST0J4R2NA0","Juspay Technologies","01M79ZZZCGHA6P27FZG2PJ2P49",827,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjuspay\u002Fxyne-spaces\u002Fblob\u002Fmain\u002Fapps\u002Fxyne-claw\u002Flearn-skills\u002Fteach-from-sources\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Teach From Sources\ndescription: Read the links or sources the user gives, in the workspace browser, and teach the topic from them — grounded, ordered, and honest about what the sources do not say.\n---\n\n# Teaching from sources\n\nUse this skill when the user asks to be taught something, or hands over links and wants them explained.\n\n## Open every source before you teach\n\nOpen each link with the browser tool so it loads in the workspace panel, then read it. The user watches the page you are reading, which is half the value: they see where the answer came from.\n\nTwo rules, and they are the difference between a tutor and a bluffer:\n\n- **Never teach from a page you could not open.** If a source fails to load, is behind a wall you cannot pass, or turns out to be something other than what its URL suggested, say so and carry on without it. Do not backfill from memory and present it as that source.\n- **Never present recall as reading.** Anything you knew before opening the sources is your own commentary. Mark it as such in one short phrase, and keep it out of the parts the user will quote.\n\nWhen the user names a topic instead of giving links, find sources first, then open them. The same rules apply.\n\n## Teach the idea, not the pages\n\nDo not walk source by source. That is a reading list, not teaching.\n\nBuild the explanation in the order someone learns it:\n\n1. **The problem it solves.** What goes wrong without this thing. One or two sentences, concrete.\n2. **The core idea.** The smallest mental model that makes the rest predictable. One idea, named plainly.\n3. **How it actually works.** The mechanism, in the order it happens. This is where a diagram earns its place.\n4. **Where it bites.** The failure modes, the surprising costs, the thing everyone gets wrong the first time.\n5. **What is still unsettled.** Where the sources disagree, or where you could not confirm.\n\nMatch the depth to what was asked. A quick orientation is a few hundred words. \"Teach me properly\" is a full pass with the mechanism worked through. Ask nothing before starting; pick from the words used and say which depth you chose in one clause.\n\n## Attribute as you go\n\nEach substantive claim names the source it came from, inline and briefly. Where two sources say different things, show both and say which is better supported and why, rather than averaging them into mush.\n\n## The lesson\n\nDeliver one self-contained HTML page named `lesson.html`, written to the workspace and delivered with the delivery tool available in this run. It holds:\n\n1. **The topic and the depth**, plus a one-sentence statement of what the reader will be able to do afterwards.\n2. **The explanation**, in the five-part order above.\n3. **A diagram** of how the pieces relate, in a `\u003Cpre class=\"mermaid\">` block with mermaid from a CDN and a dark theme. Make it clickable to expand into a fixed overlay covering the viewport, with escape to close. Never use the fullscreen API; the page is served inside a sandboxed frame where it silently fails.\n4. **Sources**, one row each: the link, what it contributed, and for anything that failed, what went wrong.\n5. **Check yourself**, three or four questions whose answers are in the lesson.\n\nNever put the page, or any fenced `html` block, in the chat reply. The chat surface reads a fenced html block as a design revision, hides your answer and replaces it with \"Design updated in preview\", and your teaching is lost. Write the file, deliver it, and teach in prose in the chat.\n\nThe chat reply is the lesson in miniature: the problem, the core idea, the mechanism in a few sentences, and the one thing people get wrong. Point at the page for the full pass.\n","# Teaching from sources\n\nUse this skill when the user asks to be taught something, or hands over links and wants them explained.\n\n## Open every source before you teach\n\nOpen each link with the browser tool so it loads in the workspace panel, then read it. The user watches the page you are reading, which is half the value: they see where the answer came from.\n\nTwo rules, and they are the difference between a tutor and a bluffer:\n\n- **Never teach from a page you could not open.** If a source fails to load, is behind a wall you cannot pass, or turns out to be something other than what its URL suggested, say so and carry on without it. Do not backfill from memory and present it as that source.\n- **Never present recall as reading.** Anything you knew before opening the sources is your own commentary. Mark it as such in one short phrase, and keep it out of the parts the user will quote.\n\nWhen the user names a topic instead of giving links, find sources first, then open them. The same rules apply.\n\n## Teach the idea, not the pages\n\nDo not walk source by source. That is a reading list, not teaching.\n\nBuild the explanation in the order someone learns it:\n\n1. **The problem it solves.** What goes wrong without this thing. One or two sentences, concrete.\n2. **The core idea.** The smallest mental model that makes the rest predictable. One idea, named plainly.\n3. **How it actually works.** The mechanism, in the order it happens. This is where a diagram earns its place.\n4. **Where it bites.** The failure modes, the surprising costs, the thing everyone gets wrong the first time.\n5. **What is still unsettled.** Where the sources disagree, or where you could not confirm.\n\nMatch the depth to what was asked. A quick orientation is a few hundred words. \"Teach me properly\" is a full pass with the mechanism worked through. Ask nothing before starting; pick from the words used and say which depth you chose in one clause.\n\n## Attribute as you go\n\nEach substantive claim names the source it came from, inline and briefly. Where two sources say different things, show both and say which is better supported and why, rather than averaging them into mush.\n\n## The lesson\n\nDeliver one self-contained HTML page named `lesson.html`, written to the workspace and delivered with the delivery tool available in this run. It holds:\n\n1. **The topic and the depth**, plus a one-sentence statement of what the reader will be able to do afterwards.\n2. **The explanation**, in the five-part order above.\n3. **A diagram** of how the pieces relate, in a `\u003Cpre class=\"mermaid\">` block with mermaid from a CDN and a dark theme. Make it clickable to expand into a fixed overlay covering the viewport, with escape to close. Never use the fullscreen API; the page is served inside a sandboxed frame where it silently fails.\n4. **Sources**, one row each: the link, what it contributed, and for anything that failed, what went wrong.\n5. **Check yourself**, three or four questions whose answers are in the lesson.\n\nNever put the page, or any fenced `html` block, in the chat reply. The chat surface reads a fenced html block as a design revision, hides your answer and replaces it with \"Design updated in preview\", and your teaching is lost. Write the file, deliver it, and teach in prose in the chat.\n\nThe chat reply is the lesson in miniature: the problem, the core idea, the mechanism in a few sentences, and the one thing people get wrong. Point at the page for the full pass.\n",{"name":5,"description":7},"main","fbefa477cb2b164d49af3ffe1b51c219b3cae6d1","apps\u002Fxyne-claw\u002Flearn-skills\u002Fteach-from-sources",573,"https:\u002F\u002Fgithub.com\u002Fjuspay\u002Fxyne-spaces","https:\u002F\u002Fxyne.ai","https:\u002F\u002Fgithub.com\u002Fjuspay","https:\u002F\u002Fwww.juspay.in"," Design to simplify. Revolutionizing digital payments.","2026-11-15 05:06:40",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add juspay\u002Fxyne-spaces --skill \"Teach From Sources\"",{"tool":40,"command":41},"bunx","bunx skills add juspay\u002Fxyne-spaces --skill \"Teach From Sources\"",{"tool":43,"command":44},"pnpm","pnpm dlx skills add juspay\u002Fxyne-spaces --skill \"Teach From Sources\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjuspay\u002Fxyne-spaces\u002Fblob\u002Fmain\u002Fapps\u002Fxyne-claw\u002Flearn-skills\u002Fteach-from-sources\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7A02Z2C9ECN1C13PE67A3DW","whoami","Show current Xyne Claw auth identity.","https:\u002F\u002Fgithub.com\u002Fjuspay\u002Fxyne-spaces\u002Fblob\u002Fmain\u002Fpackages\u002Fxyne-claw-mcp\u002Fskills\u002Fwhoami\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7A02XW56HSFGZ9PNFY3AWDT","sessions","List Xyne Claw sessions.","https:\u002F\u002Fgithub.com\u002Fjuspay\u002Fxyne-spaces\u002Fblob\u002Fmain\u002Fpackages\u002Fxyne-claw-mcp\u002Fskills\u002Fsessions\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7A02WQ3EFMNYBS0QF61JFJ6","run","Run a Xyne Claw agent.","https:\u002F\u002Fgithub.com\u002Fjuspay\u002Fxyne-spaces\u002Fblob\u002Fmain\u002Fpackages\u002Fxyne-claw-mcp\u002Fskills\u002Frun\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7A02VC1F69GS89JJBC9HCT5","login","Log the user into Xyne Claw.","https:\u002F\u002Fgithub.com\u002Fjuspay\u002Fxyne-spaces\u002Fblob\u002Fmain\u002Fpackages\u002Fxyne-claw-mcp\u002Fskills\u002Flogin\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7A02SHD94QXZ4D37P9EMW9V","agents","List available Xyne Claw agents.","https:\u002F\u002Fgithub.com\u002Fjuspay\u002Fxyne-spaces\u002Fblob\u002Fmain\u002Fpackages\u002Fxyne-claw-mcp\u002Fskills\u002Fagents\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7A02KCZS8QEARG526JJAQBZ","explanation-document","Structure a codebase\u002Fschema explanation as a self-contained HTML document ordered for a READER — mental model and flows first, deep per-component reference last — not in the order you explored it.","https:\u002F\u002Fgithub.com\u002Fjuspay\u002Fxyne-spaces\u002Fblob\u002Fmain\u002Fapps\u002Fxyne-claw\u002Funderstanding-skills\u002Fexplanation-document\u002FSKILL.md",[],[]]