[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TC8801RYJ51KC0QBJNH0F":3,"skill-same:01M79TC8801RYJ51KC0QBJNH0F":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M79TC8801RYJ51KC0QBJNH0F","ask-socrates",null,"Turn an article, social situation, decision, or practical problem into one neutral frame and exactly three tailored questions chosen from Socratic and Platonic thought tools. Use when the user asks to think like Socrates or Plato, wants a Socratic lens, or asks for three high-leverage questions that expose assumptions without a long analysis. Exclude sustained Socratic tutoring, academic history, ordinary fact-checking, and requests whose primary need is professional advice.","Mattie\u002Fmattie_skills","Mattie","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F566406?v=4","01M79TBXJN40A1D31YFHV26CY4","01M79TBXKXWGQ8X3YWDQZXDGQN",1,"MIT","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fask-socrates\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ask-socrates\ndescription: Turn an article, social situation, decision, or practical problem into one neutral frame and exactly three tailored questions chosen from Socratic and Platonic thought tools. Use when the user asks to think like Socrates or Plato, wants a Socratic lens, or asks for three high-leverage questions that expose assumptions without a long analysis. Exclude sustained Socratic tutoring, academic history, ordinary fact-checking, and requests whose primary need is professional advice.\n---\n\n# Ask Socrates\n\nCompress an inquiry into one frame and three questions. Draw from Socrates as\ndepicted in Plato's dialogues. When attribution matters, distinguish early\nSocratic inquiry from later Platonic ideas voiced by Socrates. The catalog is a\npractical synthesis; never present it as a historical ten-part system.\n\n## Establish the object of inquiry\n\nUse the article, situation, decision, or problem in the conversation. Read an\navailable source when the request depends on its contents. If there is no usable\ntopic or source, ask for the missing input and stop; apply the output contract\nafter the object of inquiry is available.\n\nPrivately reconstruct the strongest fair version of the central claim or\ninterpretation. Identify one concrete center of gravity: a claim, term, action,\nconflict, metric, expectation, or success condition. Treat the user's account as\nevidence while leaving room for other interpretations.\n\n## Choose three lenses\n\n1. Always use **Not-Knowing**. Locate the particular point where evidence ends\n   and inference, repetition, expectation, or desire begins.\n2. Rank the remaining tools by relevance to the topic, difference from the\n   Not-Knowing question, and power to reveal a consequential blind spot.\n3. Select two different tools. Prefer questions that examine different layers\n   of the topic, such as meaning and motive, evidence and character, or\n   appearance and consequence.\n\nDo not rotate tools for variety or force a famous tool onto a poor fit. Productive\nperplexity, or aporia, is a valid outcome; sharpen the uncertainty rather than\nmanufacturing a conclusion.\n\n## Use the thought tools faithfully\n\n| Label | Use it to |\n| --- | --- |\n| **Not-Knowing** | Separate what is established from what is inferred, repeated, expected, or wanted. Make the knowledge gap specific and name what could settle it. |\n| **Definition** | Ask what a central term or success condition actually means, what explains all genuine cases, and where its boundary or counterexample lies. |\n| **Elenchus** | Put two accepted commitments, examples, or consequences together and expose a tension they cannot both survive unchanged. |\n| **Midwife** | Draw out an answer already taking shape in the user's experience, then give it a test that distinguishes an owned idea from a borrowed phrase. |\n| **Perceived Good** | Ask what good each actor believes they are pursuing and where their understanding may be mistaken. Explanation must not excuse harm. |\n| **Care of the Soul** | Examine what a repeated belief, response, or practice forms in a person's character, a relationship, or a shared culture. |\n| **Euthyphro** | Separate independent merit from approval by an authority, group, expert, or audience; ask which standard could justify the approval itself. |\n| **Cave** | Identify a proxy, metric, image, story, or incentive-shaped appearance that may be mistaken for the underlying reality. |\n| **Divided Soul** | Distinguish reason from status or anger and from comfort, fear, or appetite when a person is pulled in different directions. Avoid diagnosis. |\n| **Hypothesis** | Assume a claim temporarily, derive a concrete observable consequence, and test whether the consequences cohere with one another and the situation. |\n\n## Ground the questions in context\n\n- For an **article**, use the author's actual claim, evidence, key term, or\n  authority. Invent no missing premise or source detail.\n- For a **social situation**, distinguish observed behavior from inferred motive.\n  Examine the user's interpretation as readily as another person's and avoid\n  blame, diagnosis, or therapeutic authority.\n- For a **decision or practical problem**, clarify the desired outcome and\n  constraints, challenge a load-bearing assumption, and consider downstream\n  incentives or habits when relevant.\n\nEvery question must name a concrete claim, term, action, actor, metric, or\nrelationship from the input. A philosophical label without its reasoning pattern\nis a failed question.\n\n## Return the result\n\nUse exactly this default shape:\n\n```markdown\nFrame: \u003Cone neutral sentence identifying the live issue>\n\n1. **Not-Knowing:** \u003Cone tailored question?>\n2. **\u003Cselected tool>:** \u003Cone tailored question?>\n3. **\u003Cselected tool>:** \u003Cone tailored question?>\n```\n\nThe frame is one declarative sentence and gives no verdict. Return exactly three\nquestions, each one sentence long. The second and third labels must be distinct\nnames from the catalog. Keep the questions crisp, concrete, and capable of\nchanging how the topic is framed.\n\nBy default, include no answers, advice, quotations, philosophical exposition, or\nexplanation of tool selection. Avoid role-playing Socrates, invented quotations,\nmoral verdicts, and unnecessary Greek vocabulary.\n\nWhen the user explicitly requests another deliverable, return the intact frame\nand three questions first, then put the additional work under a separate heading.\n\n## Check the three questions\n\nBefore responding, confirm that:\n\n- **Not-Knowing** identifies a real and specific epistemic gap.\n- The selected tools address different aspects of the topic.\n- Each question uses the reasoning pattern promised by its label.\n- Each question is grounded closely enough that it would not fit an unrelated\n  article, situation, or problem without substantial rewriting.\n- Any remaining uncertainty is clearer and more useful than it was before.\n","# Ask Socrates\n\nCompress an inquiry into one frame and three questions. Draw from Socrates as\ndepicted in Plato's dialogues. When attribution matters, distinguish early\nSocratic inquiry from later Platonic ideas voiced by Socrates. The catalog is a\npractical synthesis; never present it as a historical ten-part system.\n\n## Establish the object of inquiry\n\nUse the article, situation, decision, or problem in the conversation. Read an\navailable source when the request depends on its contents. If there is no usable\ntopic or source, ask for the missing input and stop; apply the output contract\nafter the object of inquiry is available.\n\nPrivately reconstruct the strongest fair version of the central claim or\ninterpretation. Identify one concrete center of gravity: a claim, term, action,\nconflict, metric, expectation, or success condition. Treat the user's account as\nevidence while leaving room for other interpretations.\n\n## Choose three lenses\n\n1. Always use **Not-Knowing**. Locate the particular point where evidence ends\n   and inference, repetition, expectation, or desire begins.\n2. Rank the remaining tools by relevance to the topic, difference from the\n   Not-Knowing question, and power to reveal a consequential blind spot.\n3. Select two different tools. Prefer questions that examine different layers\n   of the topic, such as meaning and motive, evidence and character, or\n   appearance and consequence.\n\nDo not rotate tools for variety or force a famous tool onto a poor fit. Productive\nperplexity, or aporia, is a valid outcome; sharpen the uncertainty rather than\nmanufacturing a conclusion.\n\n## Use the thought tools faithfully\n\n| Label | Use it to |\n| --- | --- |\n| **Not-Knowing** | Separate what is established from what is inferred, repeated, expected, or wanted. Make the knowledge gap specific and name what could settle it. |\n| **Definition** | Ask what a central term or success condition actually means, what explains all genuine cases, and where its boundary or counterexample lies. |\n| **Elenchus** | Put two accepted commitments, examples, or consequences together and expose a tension they cannot both survive unchanged. |\n| **Midwife** | Draw out an answer already taking shape in the user's experience, then give it a test that distinguishes an owned idea from a borrowed phrase. |\n| **Perceived Good** | Ask what good each actor believes they are pursuing and where their understanding may be mistaken. Explanation must not excuse harm. |\n| **Care of the Soul** | Examine what a repeated belief, response, or practice forms in a person's character, a relationship, or a shared culture. |\n| **Euthyphro** | Separate independent merit from approval by an authority, group, expert, or audience; ask which standard could justify the approval itself. |\n| **Cave** | Identify a proxy, metric, image, story, or incentive-shaped appearance that may be mistaken for the underlying reality. |\n| **Divided Soul** | Distinguish reason from status or anger and from comfort, fear, or appetite when a person is pulled in different directions. Avoid diagnosis. |\n| **Hypothesis** | Assume a claim temporarily, derive a concrete observable consequence, and test whether the consequences cohere with one another and the situation. |\n\n## Ground the questions in context\n\n- For an **article**, use the author's actual claim, evidence, key term, or\n  authority. Invent no missing premise or source detail.\n- For a **social situation**, distinguish observed behavior from inferred motive.\n  Examine the user's interpretation as readily as another person's and avoid\n  blame, diagnosis, or therapeutic authority.\n- For a **decision or practical problem**, clarify the desired outcome and\n  constraints, challenge a load-bearing assumption, and consider downstream\n  incentives or habits when relevant.\n\nEvery question must name a concrete claim, term, action, actor, metric, or\nrelationship from the input. A philosophical label without its reasoning pattern\nis a failed question.\n\n## Return the result\n\nUse exactly this default shape:\n\n```markdown\nFrame: \u003Cone neutral sentence identifying the live issue>\n\n1. **Not-Knowing:** \u003Cone tailored question?>\n2. **\u003Cselected tool>:** \u003Cone tailored question?>\n3. **\u003Cselected tool>:** \u003Cone tailored question?>\n```\n\nThe frame is one declarative sentence and gives no verdict. Return exactly three\nquestions, each one sentence long. The second and third labels must be distinct\nnames from the catalog. Keep the questions crisp, concrete, and capable of\nchanging how the topic is framed.\n\nBy default, include no answers, advice, quotations, philosophical exposition, or\nexplanation of tool selection. Avoid role-playing Socrates, invented quotations,\nmoral verdicts, and unnecessary Greek vocabulary.\n\nWhen the user explicitly requests another deliverable, return the intact frame\nand three questions first, then put the additional work under a separate heading.\n\n## Check the three questions\n\nBefore responding, confirm that:\n\n- **Not-Knowing** identifies a real and specific epistemic gap.\n- The selected tools address different aspects of the topic.\n- Each question uses the reasoning pattern promised by its label.\n- Each question is grounded closely enough that it would not fit an unrelated\n  article, situation, or problem without substantial rewriting.\n- Any remaining uncertainty is clearer and more useful than it was before.\n",{"name":5,"description":7},"main","9d47db883531c45e29672090c38080c58434b2ac","skills\u002Fask-socrates",0,"https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills","https:\u002F\u002Fgithub.com\u002FMattie","2026-11-11 04:41:31",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Mattie\u002Fmattie_skills --skill ask-socrates",{"tool":36,"command":37},"bunx","bunx skills add Mattie\u002Fmattie_skills --skill ask-socrates",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Mattie\u002Fmattie_skills --skill ask-socrates","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fask-socrates\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",294,"https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fask-socrates\u002Fagents\u002Fopenai.yaml",[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M79TFVB2DE2KYVNN2M8TF2Y7","write-simplified-technical-english","Write, rewrite, or review technical content with ASD-STE100 Simplified Technical English (STE), Issue 9. Use only when the user explicitly invokes $write-simplified-technical-english. Common requests mention ASD-STE100, STE, or \"write STE\"; do not use for general requests for clear, simple, concise, or technical writing.","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-simplified-technical-english\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M79TFMJCP75Z4GP1KYZAYS6D","write-plainly","Write, rewrite, or review prose in plain language for its intended reader while preserving technical meaning, constraints, uncertainty, and protected literals. Use when the user asks for plain language or plain English, audience-appropriate clarity, an easier-to-understand explanation, or a meaning-preserving simplification of technical prose. When one of those triggers applies, use for public information, documentation, instructions, explanations, notices, and interface text. Do not invoke solely for proofreading, shortening, generic copyediting, humanizing prose, removing AI tells, marketing voice, or creative rewriting. When the user explicitly requests ASD-STE100, STE, or invokes $write-simplified-technical-english, use that skill instead.","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plainly\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M79TFBYC0GZ9YRR116EM267V","write-humanly","Draft, rewrite, or review prose so it sounds like a particular human had a reason to write it. Use when the user asks for human-sounding or less AI-ish writing, dislikes the wording or tone, wants anti-AI prose review or voice matching from supplied human text, needs an existing document's voice preserved, or wants familiar LLM habits removed, such as corrective antithesis, triplets, stock metaphors, prestige filler, needless em dashes, generic assistant language, and performative confidence. Do not invoke solely for plain language, proofreading, shortening, generic copyediting, or a change in formality. Use only when the request concerns human voice, authorial character, or generated-prose texture.","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-humanly\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M79TF7FDRZT52QCH1CJEK578","what-what","The user is asking: What is this thread (or main thread) asking for here? Give it to me and $write-humanly. What is even the context? What changes?","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhat-what\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M79TF445Z9P7WCN4B8C4QF4A","what-huh","Make final responses understandable to a reader who cannot see the agent's working text, especially when reporting progress, explaining findings, or asking for a decision.","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhat-huh\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M79TF04KA3NCW5NFB34B7JP2","verifier-system","Establish and keep a project's verification practice useful through Surface, Answer Key, and Comparison. Use for setup verifier-system, choosing how to verify agentic changes, or updating a project's verification guidance as its components evolve.","https:\u002F\u002Fgithub.com\u002FMattie\u002Fmattie_skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifier-system\u002FSKILL.md",[],[]]