[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79EP001PCMW2G1013A867BF":3,"skill-same:01M79EP001PCMW2G1013A867BF":58},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":14,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M79EP001PCMW2G1013A867BF","method-simplification",null,"Audit a plan, experiment design, algorithm, probe, analysis script, test code, workflow, or research artifact for unnecessary complexity. Use when the user asks to \"simplify the method\", \"reduce complexity\", \"remove unnecessary parts\", \"tighten this experiment\", \"find the minimal deterministic path\", or wants an audit that preserves the exact research or implementation contract while eliminating avoidable moving parts.","zfifteen\u002Fskills-catalog","zfifteen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221906715?v=4","01M79CQFXDZM5J5CJTCECPFA66","Dionisio Alberto Lopez III","01M79CQFY4C62PN8A2T5KDAHGA",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fmethod-simplification\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: method-simplification\ndescription: >\n  Audit a plan, experiment design, algorithm, probe, analysis script, test\n  code, workflow, or research artifact for unnecessary complexity. Use when\n  the user asks to \"simplify the method\", \"reduce complexity\", \"remove\n  unnecessary parts\", \"tighten this experiment\", \"find the minimal\n  deterministic path\", or wants an audit that preserves the exact research or\n  implementation contract while eliminating avoidable moving parts.\nwhen-to-use: \"Before accepting a method as good enough; when reviewing or designing experiments, algorithms, workflows, or code for methodological compression (not generic cleanup). Trigger phrases include 'simplify', 'minimal version', 'too much branching', 'overbuilt'.\"\nallowed-tools: [\"read_file\", \"grep\", \"list_dir\", \"search_replace\", \"write\", \"grep\", \"task\"]\nargument-hint: \"\u003Cdescription or path to the method\u002Fplan\u002Fartifact to audit> [optional: the exact contract it must preserve]\"\nmetadata:\n  short-description: \"Methodological compression audit: remove avoidable complexity while strictly preserving the research\u002Fimplementation contract\"\n  canonical-codex-skill: \"\u002FUsers\u002Fvelocityworks\u002F.codex\u002Fskills\u002Fmethod-simplification\u002FSKILL.md\"\n---\n\n# Method Simplification\n\n## Purpose\n\nBefore accepting any method (plan, algorithm, probe, experiment, test, analysis script, or workflow) as \"good enough,\" audit it for avoidable complexity. The goal is **methodological compression** while preserving the exact contract the method is supposed to satisfy.\n\nA valid simplification must keep the same:\n- Hypothesis or question being answered\n- Observable or invariant being measured\n- Input regime and acceptance\u002Ffailure conditions\n- Validity boundaries\n\nSimplification by weakening the claim, dropping a necessary control, hiding uncertainty, or replacing a precise contract with a vague one is forbidden.\n\n## Core Contract\n\nPrefer the smallest deterministic method that answers the exact question with:\n- Fewer moving parts\n- Less branching and state\n- Fewer repeated computations (compute once, reuse)\n- Clearer auditability and reproducibility\n- Explicit failure modes instead of silent fallback or resilient degradation\n\n## Audit Workflow\n\n1. **Identify the target**\n   - The artifact under review (plan text, algorithm description, pseudocode, source files, experiment protocol, script, etc.).\n   - Use `read_file`, `grep`, `list_dir` to load it precisely.\n\n2. **State the contract (one or two sentences)**\n   - What exact question or invariant must the method answer or protect?\n   - What are the input regime, success condition, and failure condition?\n   - If the user provided a contract statement, use it verbatim; otherwise derive the tightest faithful version from the artifact and context and confirm.\n\n3. **Separate necessary vs. avoidable complexity**\n   - Trace every branch, helper, repeated computation, abstraction, fallback, config surface, or extra measurement back to the contract.\n   - Keep only if removing it would change the answer, the measured object, or the validity boundary.\n\n4. **Propose the minimal replacement**\n   - Give the smaller method as concrete steps, pseudocode, edit plan (using search_replace targets), or a narrow script.\n   - The replacement must be narrow enough that another agent can implement it without inventing new modes or abstractions.\n\n5. **Name what must not change**\n   - Explicitly list any complexity that protects the contract and must remain.\n\n6. **State residual risk**\n   - Any limits, assumptions, or checks still required after simplification.\n   - If none material, state: \"No material residual risk identified under the stated contract.\"\n\n## What to Look For (Common Targets)\n\n- Unnecessary branching, mode flags, or \"if this then that\" logic\n- Repeated computations that can be hoisted or memoized once\n- Helpers, base classes, or frameworks that do not reduce current complexity for this specific contract\n- Broad workflows where a straight-line script or single-pass analysis would suffice\n- Hidden fallback logic, retries, alternate paths, or silent degradation\n- Non-determinism where a deterministic construction is possible\n- Measurements, probes, or tests that do not affect the conclusion or decision\n- Output artifacts that make the result harder (rather than easier) to audit or reproduce\n\n## Output Shape (Use This Structure)\n\n1. **Contract Preserved**\n   - One or two sentences stating the exact question\u002Finvariant the simplified method must protect.\n\n2. **Complexity Findings**\n   - Bulleted list of only the avoidable complexity that impacts auditability, runtime, reproducibility, or semantic clarity.\n   - For each: \"This X is unnecessary because \u003Ctrace to contract>; removing it does not change Y.\"\n\n3. **Simplified Method**\n   - Concrete replacement: numbered steps, pseudocode block, or precise edit plan with file:line anchors.\n   - Narrow enough for direct implementation.\n\n4. **What Not To Change**\n   - Explicit list of retained complexity and why it is required by the contract.\n\n5. **Residual Risk**\n   - \"No material residual risk identified under the stated contract.\" (or the precise remaining items).\n\n## Stop Conditions\n\n- **No simplification recommended**: Every apparent complexity is required by the contract or its removal would alter the measured object, validity boundary, acceptance condition, or failure condition. State this clearly.\n\n- **Shape feels wrong**: The current method is answering a different question than the user asked. Surface the contract mismatch first, before any simplification proposal.\n\n## Guardrails\n\n- This is **not** a generic code-style or lint review. Focus exclusively on methodological \u002F contract fidelity.\n- Do not optimize for future extensibility unless extensibility is part of the user's stated contract.\n- Never introduce new frameworks, config surfaces, fallback paths, extra modes, or helper subsystems as part of the \"simplification.\"\n- Shorter is not automatically better if it obscures the method or weakens reviewability.\n- Controls, checks, and explicit failure cases that protect the conclusion must stay.\n- Never present a simplification as valid unless you have verified the original contract is fully preserved.\n- In PGS or deterministic research contexts, treat the PGS rule\u002Flaw and invariant set as part of the contract that must not be weakened.\n\n## Success Criteria\n\n- The auditor can point to a specific, smaller method that still satisfies the identical contract.\n- Any retained complexity is explicitly justified by the contract.\n- The output is immediately actionable by an implementer or experimenter.\n- If no simplification is possible, the user receives a crisp explanation rather than a vague \"it looks okay.\"\n\nUse this skill early in experiment or algorithm design and before large implementation efforts.\n","# Method Simplification\n\n## Purpose\n\nBefore accepting any method (plan, algorithm, probe, experiment, test, analysis script, or workflow) as \"good enough,\" audit it for avoidable complexity. The goal is **methodological compression** while preserving the exact contract the method is supposed to satisfy.\n\nA valid simplification must keep the same:\n- Hypothesis or question being answered\n- Observable or invariant being measured\n- Input regime and acceptance\u002Ffailure conditions\n- Validity boundaries\n\nSimplification by weakening the claim, dropping a necessary control, hiding uncertainty, or replacing a precise contract with a vague one is forbidden.\n\n## Core Contract\n\nPrefer the smallest deterministic method that answers the exact question with:\n- Fewer moving parts\n- Less branching and state\n- Fewer repeated computations (compute once, reuse)\n- Clearer auditability and reproducibility\n- Explicit failure modes instead of silent fallback or resilient degradation\n\n## Audit Workflow\n\n1. **Identify the target**\n   - The artifact under review (plan text, algorithm description, pseudocode, source files, experiment protocol, script, etc.).\n   - Use `read_file`, `grep`, `list_dir` to load it precisely.\n\n2. **State the contract (one or two sentences)**\n   - What exact question or invariant must the method answer or protect?\n   - What are the input regime, success condition, and failure condition?\n   - If the user provided a contract statement, use it verbatim; otherwise derive the tightest faithful version from the artifact and context and confirm.\n\n3. **Separate necessary vs. avoidable complexity**\n   - Trace every branch, helper, repeated computation, abstraction, fallback, config surface, or extra measurement back to the contract.\n   - Keep only if removing it would change the answer, the measured object, or the validity boundary.\n\n4. **Propose the minimal replacement**\n   - Give the smaller method as concrete steps, pseudocode, edit plan (using search_replace targets), or a narrow script.\n   - The replacement must be narrow enough that another agent can implement it without inventing new modes or abstractions.\n\n5. **Name what must not change**\n   - Explicitly list any complexity that protects the contract and must remain.\n\n6. **State residual risk**\n   - Any limits, assumptions, or checks still required after simplification.\n   - If none material, state: \"No material residual risk identified under the stated contract.\"\n\n## What to Look For (Common Targets)\n\n- Unnecessary branching, mode flags, or \"if this then that\" logic\n- Repeated computations that can be hoisted or memoized once\n- Helpers, base classes, or frameworks that do not reduce current complexity for this specific contract\n- Broad workflows where a straight-line script or single-pass analysis would suffice\n- Hidden fallback logic, retries, alternate paths, or silent degradation\n- Non-determinism where a deterministic construction is possible\n- Measurements, probes, or tests that do not affect the conclusion or decision\n- Output artifacts that make the result harder (rather than easier) to audit or reproduce\n\n## Output Shape (Use This Structure)\n\n1. **Contract Preserved**\n   - One or two sentences stating the exact question\u002Finvariant the simplified method must protect.\n\n2. **Complexity Findings**\n   - Bulleted list of only the avoidable complexity that impacts auditability, runtime, reproducibility, or semantic clarity.\n   - For each: \"This X is unnecessary because \u003Ctrace to contract>; removing it does not change Y.\"\n\n3. **Simplified Method**\n   - Concrete replacement: numbered steps, pseudocode block, or precise edit plan with file:line anchors.\n   - Narrow enough for direct implementation.\n\n4. **What Not To Change**\n   - Explicit list of retained complexity and why it is required by the contract.\n\n5. **Residual Risk**\n   - \"No material residual risk identified under the stated contract.\" (or the precise remaining items).\n\n## Stop Conditions\n\n- **No simplification recommended**: Every apparent complexity is required by the contract or its removal would alter the measured object, validity boundary, acceptance condition, or failure condition. State this clearly.\n\n- **Shape feels wrong**: The current method is answering a different question than the user asked. Surface the contract mismatch first, before any simplification proposal.\n\n## Guardrails\n\n- This is **not** a generic code-style or lint review. Focus exclusively on methodological \u002F contract fidelity.\n- Do not optimize for future extensibility unless extensibility is part of the user's stated contract.\n- Never introduce new frameworks, config surfaces, fallback paths, extra modes, or helper subsystems as part of the \"simplification.\"\n- Shorter is not automatically better if it obscures the method or weakens reviewability.\n- Controls, checks, and explicit failure cases that protect the conclusion must stay.\n- Never present a simplification as valid unless you have verified the original contract is fully preserved.\n- In PGS or deterministic research contexts, treat the PGS rule\u002Flaw and invariant set as part of the contract that must not be weakened.\n\n## Success Criteria\n\n- The auditor can point to a specific, smaller method that still satisfies the identical contract.\n- Any retained complexity is explicitly justified by the contract.\n- The output is immediately actionable by an implementer or experimenter.\n- If no simplification is possible, the user receives a crisp explanation rather than a vague \"it looks okay.\"\n\nUse this skill early in experiment or algorithm design and before large implementation efforts.\n",{"name":5,"metadata":24,"description":27,"when-to-use":28,"allowed-tools":29,"argument-hint":36},{"short-description":25,"canonical-codex-skill":26},"Methodological compression audit: remove avoidable complexity while strictly preserving the research\u002Fimplementation contract","\u002FUsers\u002Fvelocityworks\u002F.codex\u002Fskills\u002Fmethod-simplification\u002FSKILL.md","Audit a plan, experiment design, algorithm, probe, analysis script, test code, workflow, or research artifact for unnecessary complexity. Use when the user asks to \"simplify the method\", \"reduce complexity\", \"remove unnecessary parts\", \"tighten this experiment\", \"find the minimal deterministic path\", or wants an audit that preserves the exact research or implementation contract while eliminating avoidable moving parts.\n","Before accepting a method as good enough; when reviewing or designing experiments, algorithms, workflows, or code for methodological compression (not generic cleanup). Trigger phrases include 'simplify', 'minimal version', 'too much branching', 'overbuilt'.",[30,31,32,33,34,31,35],"read_file","grep","list_dir","search_replace","write","task","\u003Cdescription or path to the method\u002Fplan\u002Fartifact to audit> [optional: the exact contract it must preserve]","main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Fmethod-simplification","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002Fzfifteen","I like to measure things.","2026-07-19 23:41:54",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add zfifteen\u002Fskills-catalog --skill method-simplification",{"tool":50,"command":51},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill method-simplification",{"tool":53,"command":54},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill method-simplification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fmethod-simplification\u002FSKILL.md",true,[],[59,66,73,80,89,96],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79GXQ2PWPT2E4CJYHXVJ0YE","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79GXN85NETKBE06865CWK6Z","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79GXCYD7FGYS932J9N9RFFY","youtube","Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript.  Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or \"what does this video actually say\".  The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content.  Triggers: \"youtube transcript\", \"get the transcript of this video\", \"summarize this youtube video\", \"what did they say in https:\u002F\u002Fyoutube.com\u002F...\", \"key claims from this talk\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79GX8EXHHYM566BKR7MS778","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79GX2HFJPX84NMRE5VBTYX9","x-post-creator","Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, \u002Fx-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs\u002Fx-posts\u002F[story-name]\u002F.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-post-creator\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M79GWXQT4HBT6QME6QSBZJFA","x-api","Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X\u002Fx.com, reading threads and replies, creating lists, staging\u002Fpublishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions \u002Fx-api or \"search X\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]