[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E800PC457EHCER3586C29B":3,"skill-same:01M7E800PC457EHCER3586C29B":85},{"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":36,"commitSha":37,"skillDirectory":38,"forksCount":14,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":56},"01M7E800PC457EHCER3586C29B","scholar-distill",null,"Build source-supported types, memberships, and controlled vocabulary from a term table","tony\u002Fskills","tony","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F26336?v=4","01M72E5RNJ7SQV8F9KBM5RKRMN","Tony Narlock","01M7E7MBN5C6YZ4JJJ5Y82KBJG",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscholar-distill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: scholar-distill\ndescription: >-\n  Build source-supported types, memberships, and controlled vocabulary from\n  a term table\ndisable-model-invocation: true\nallowed-tools: [\"Bash\", \"Read\", \"Grep\", \"Glob\", \"Edit\", \"Write\", \"AskUserQuestion\"]\nmetadata:\n  argument-hint: \"[--out=\u003Cdir>]\"\n  source: \"plugins\u002Fscholar\u002Fskills\u002Fdistill\u002FSKILL.md\"\n---\n\n# this skill\n\nStage 3. Turn a flat term table into an ontology. Three layers, in order. Any\none of them alone is not an ontology.\n\nRead `references\u002Fevidence-tiers.md` for what each claim must carry and\n`references\u002Fstage-gates.md` for this stage's exit condition. The analyzer\nis `references\u002Fterm_metrics.py`; `\u003Canalyzer>` below is its absolute path\nresolved from this skill's directory.\n\nUser arguments: $ARGUMENTS\n\nRead `references\u002Foutput-contract.md` before writing study files.\n\n## Layer 1: types\n\nThe is-a hierarchy. What kinds of thing the corpus contains.\n\nWrite it to `evidence\u002Fhierarchy.md`, citing each type declaration and is-a\nclaim. Each type is also a row in `terms.jsonl` with `kind: type`, its\ncorpus-supported `definition`, and `parent` set to another type or the literal\nstring `root`.\nWrite each type's name onto its members' rows as `parent`. A type row you create\ncarries `\"schema\": 1` and no `cites`; the gate exempts it\n(`references\u002Fstage-gates.md`), and the citations live in `hierarchy.md`. A type the corpus\nalready names (a `class`) keeps the row `extract` wrote: change its `kind` from\n`class` to `type` in place, `cites` included.\n\nEach non-root parent needs a source-supported is-a or member relation.\nSharing a file, directory, or prefix does not establish that relation.\n`root` is the special anchor for top-level types, not an invented type.\n\n## Layer 2: supported memberships\n\nRecord the corpus's basis for membership in `evidence\u002Fhierarchy.md`. A code\ndeclaration supports a named type even when the corpus gives no behavioral\nmembership test. Keep its documented role separate from that declaration.\n\nUse a necessary-and-sufficient discriminator only when the source establishes\nboth directions. A docstring describing a type's role does not establish that\neverything with that role belongs to the type, or that its members have no\nother roles. Keep the extracted definition and citations; do not strengthen\na role description into such a test.\n\nAn analyst-proposed type without a supported membership relation remains\nunsupported. Record the gap rather than inventing a type or parent.\n\n## Layer 3: the controlled vocabulary\n\nWrite `evidence\u002Fvocabulary.md`: the corpus's terms, their senses, preferred\nspellings, observed aliases, and any source-declared deprecations.\n\nPreserve supported synonymy, multiple senses, and overlap. Cite each asserted\nequivalence or disjointness constraint; sibling placement does not imply\ndisjointness. When the source leaves a relationship unknown, record that\nlimit without asserting either overlap or exclusion. Lexical similarity\nproposes a question for `contest`, not a semantic relation.\n\nThe preferred term is the one the corpus already uses most, not the one that\nreads best. A vocabulary that renames what the corpus says has stopped\ndescribing it.\n\n## The orphan gate\n\nRun the term gate and the hierarchy gate from\n`references\u002Fstage-gates.md`; both must exit zero:\n\n```console\n$ python3 \u003Canalyzer> notes\u002Fontology\u002F\u003Csubject>\u002F --check-terms\n```\n\n```console\n$ python3 \u003Canalyzer> notes\u002Fontology\u002F\u003Csubject>\u002F --check-hierarchy\n```\n\nFix each cycle by re-reading the corpus's own is-a claim. An orphan\nmay be a valid term whose parent the corpus does not establish. Retain it\nand report the failed gate. Do not drop it or promote it without source\nsupport to clear a finding. Never invent a type to house an orphan or split\na type to tidy its fan-out.\n\n## Rules\n\n- A term keeps the spelling `extract` recorded. The vocabulary names a\n  preferred term; it does not rewrite the rows.\n- Deprecated variants stay in the table. They are what a reader of the corpus\n  will actually encounter.\n\n## Output\n\nPer `references\u002Foutput-contract.md`. Hero: `✓ \u003Cn> types, \u003Cn> terms, \u003Cn>\npreferred terms`, `⚠ Gate failed: \u003Cn> orphans, \u003Cn> cycles`, or `⚠ Blocked:\n\u003Creason>`. A failed gate lists each orphan or cycle on its own line, then one\nsentence naming the terms whose corpus evidence must be re-read before\nassigning parents (no quoted corpus text, not even in parentheses):\n\n```text\n⚠ Gate failed: 1 orphan, 1 cycle\n\n- Orphan: checkpoint\n- Cycle: phase -> stage -> phase\n\nRe-read the corpus evidence for checkpoint, stage, and phase before assigning parents, then rerun the gate.\n```\n\nSections:\n\n1. `## Types`: the hierarchy and each type's supported membership basis.\n2. `## Vocabulary`: preferred terms with their deprecated variants.\n3. `## Unresolved`: terms that resisted placement, and what that suggests\n   about the corpus rather than about the table.\n\nNext-step options: run contest, revisit a type, stop here.\n\nWrite it per `references\u002Fprose-rules.md`.\n\n\n## Portability notes\n\n- `$ARGUMENTS` — the text the user passed when invoking this skill. If your host does not substitute it, read it as the user's request in the current turn, and ask when there is none.\n- Bundled files — every relative path in this skill points at a file shipped inside this skill directory. Read them from here, not from the host's plugin tree.\n","# this skill\n\nStage 3. Turn a flat term table into an ontology. Three layers, in order. Any\none of them alone is not an ontology.\n\nRead `references\u002Fevidence-tiers.md` for what each claim must carry and\n`references\u002Fstage-gates.md` for this stage's exit condition. The analyzer\nis `references\u002Fterm_metrics.py`; `\u003Canalyzer>` below is its absolute path\nresolved from this skill's directory.\n\nUser arguments: $ARGUMENTS\n\nRead `references\u002Foutput-contract.md` before writing study files.\n\n## Layer 1: types\n\nThe is-a hierarchy. What kinds of thing the corpus contains.\n\nWrite it to `evidence\u002Fhierarchy.md`, citing each type declaration and is-a\nclaim. Each type is also a row in `terms.jsonl` with `kind: type`, its\ncorpus-supported `definition`, and `parent` set to another type or the literal\nstring `root`.\nWrite each type's name onto its members' rows as `parent`. A type row you create\ncarries `\"schema\": 1` and no `cites`; the gate exempts it\n(`references\u002Fstage-gates.md`), and the citations live in `hierarchy.md`. A type the corpus\nalready names (a `class`) keeps the row `extract` wrote: change its `kind` from\n`class` to `type` in place, `cites` included.\n\nEach non-root parent needs a source-supported is-a or member relation.\nSharing a file, directory, or prefix does not establish that relation.\n`root` is the special anchor for top-level types, not an invented type.\n\n## Layer 2: supported memberships\n\nRecord the corpus's basis for membership in `evidence\u002Fhierarchy.md`. A code\ndeclaration supports a named type even when the corpus gives no behavioral\nmembership test. Keep its documented role separate from that declaration.\n\nUse a necessary-and-sufficient discriminator only when the source establishes\nboth directions. A docstring describing a type's role does not establish that\neverything with that role belongs to the type, or that its members have no\nother roles. Keep the extracted definition and citations; do not strengthen\na role description into such a test.\n\nAn analyst-proposed type without a supported membership relation remains\nunsupported. Record the gap rather than inventing a type or parent.\n\n## Layer 3: the controlled vocabulary\n\nWrite `evidence\u002Fvocabulary.md`: the corpus's terms, their senses, preferred\nspellings, observed aliases, and any source-declared deprecations.\n\nPreserve supported synonymy, multiple senses, and overlap. Cite each asserted\nequivalence or disjointness constraint; sibling placement does not imply\ndisjointness. When the source leaves a relationship unknown, record that\nlimit without asserting either overlap or exclusion. Lexical similarity\nproposes a question for `contest`, not a semantic relation.\n\nThe preferred term is the one the corpus already uses most, not the one that\nreads best. A vocabulary that renames what the corpus says has stopped\ndescribing it.\n\n## The orphan gate\n\nRun the term gate and the hierarchy gate from\n`references\u002Fstage-gates.md`; both must exit zero:\n\n```console\n$ python3 \u003Canalyzer> notes\u002Fontology\u002F\u003Csubject>\u002F --check-terms\n```\n\n```console\n$ python3 \u003Canalyzer> notes\u002Fontology\u002F\u003Csubject>\u002F --check-hierarchy\n```\n\nFix each cycle by re-reading the corpus's own is-a claim. An orphan\nmay be a valid term whose parent the corpus does not establish. Retain it\nand report the failed gate. Do not drop it or promote it without source\nsupport to clear a finding. Never invent a type to house an orphan or split\na type to tidy its fan-out.\n\n## Rules\n\n- A term keeps the spelling `extract` recorded. The vocabulary names a\n  preferred term; it does not rewrite the rows.\n- Deprecated variants stay in the table. They are what a reader of the corpus\n  will actually encounter.\n\n## Output\n\nPer `references\u002Foutput-contract.md`. Hero: `✓ \u003Cn> types, \u003Cn> terms, \u003Cn>\npreferred terms`, `⚠ Gate failed: \u003Cn> orphans, \u003Cn> cycles`, or `⚠ Blocked:\n\u003Creason>`. A failed gate lists each orphan or cycle on its own line, then one\nsentence naming the terms whose corpus evidence must be re-read before\nassigning parents (no quoted corpus text, not even in parentheses):\n\n```text\n⚠ Gate failed: 1 orphan, 1 cycle\n\n- Orphan: checkpoint\n- Cycle: phase -> stage -> phase\n\nRe-read the corpus evidence for checkpoint, stage, and phase before assigning parents, then rerun the gate.\n```\n\nSections:\n\n1. `## Types`: the hierarchy and each type's supported membership basis.\n2. `## Vocabulary`: preferred terms with their deprecated variants.\n3. `## Unresolved`: terms that resisted placement, and what that suggests\n   about the corpus rather than about the table.\n\nNext-step options: run contest, revisit a type, stop here.\n\nWrite it per `references\u002Fprose-rules.md`.\n\n\n## Portability notes\n\n- `$ARGUMENTS` — the text the user passed when invoking this skill. If your host does not substitute it, read it as the user's request in the current turn, and ask when there is none.\n- Bundled files — every relative path in this skill points at a file shipped inside this skill directory. Read them from here, not from the host's plugin tree.\n",{"name":5,"metadata":24,"description":7,"allowed-tools":27,"disable-model-invocation":35},{"source":25,"argument-hint":26},"plugins\u002Fscholar\u002Fskills\u002Fdistill\u002FSKILL.md","[--out=\u003Cdir>]",[28,29,30,31,32,33,34],"Bash","Read","Grep","Glob","Edit","Write","AskUserQuestion",true,"main","5fbeb3b47beedea13813be7b7023f736a8d97a65",".agents\u002Fskills\u002Fscholar-distill","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills","https:\u002F\u002Fgithub.com\u002Ftony","https:\u002F\u002Ftony.sh","lighthouse keeper","2026-11-08 17:57:34",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":35},[46,49,52],{"tool":47,"command":48},"npx","npx skills add tony\u002Fskills --skill scholar-distill",{"tool":50,"command":51},"bunx","bunx skills add tony\u002Fskills --skill scholar-distill",{"tool":53,"command":54},"pnpm","pnpm dlx skills add tony\u002Fskills --skill scholar-distill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscholar-distill\u002FSKILL.md",[57,63,67,71,75,79],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"agents\u002Fopenai.yaml","REFERENCE","参考文档",288,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscholar-distill\u002Fagents\u002Fopenai.yaml",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fevidence-tiers.md",1759,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscholar-distill\u002Freferences\u002Fevidence-tiers.md",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Foutput-contract.md",4098,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscholar-distill\u002Freferences\u002Foutput-contract.md",{"path":72,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fprose-rules.md",4644,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscholar-distill\u002Freferences\u002Fprose-rules.md",{"path":76,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fstage-gates.md",4310,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscholar-distill\u002Freferences\u002Fstage-gates.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fterm_metrics.py","SCRIPT","脚本",48954,"https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscholar-distill\u002Freferences\u002Fterm_metrics.py",[86,93,100,107,114,121],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7E8NCSHXV2JPW4J61R0TQS7","serene-bliss","Use when asked to make a CLI --help, docs page, error message, or tooling UX more serene or calmer for developer experience; returns text, no edits.","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Fserene-bliss\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7E8N87MAVJD8RRQKQB1ZPS6","review","Weave code review: run independent adversarial reviews in parallel, then synthesize findings","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7E8N402XG4ZBFNACQ413163","refine","Use when asked to refine a draft, iterate on code until cleaner, or polish a README through repeated critique and improvement.","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Frefine\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7E8N01KB86A7136P00GVKJW","prompt","Weave prompt: compare independent adversarial implementations, then adopt the single best one","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Fprompt\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7E8MW7YJW2PCMDW3G9RTGNK","plan","Weave planning: compare independent adversarial plans, then synthesize the best one","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Fplan\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M7E8MSBYXNCV4ZYWDS4PFJXK","fix-review","Fix weave review findings: validate, add test coverage, fix, and commit each as atomic changes","https:\u002F\u002Fgithub.com\u002Ftony\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fweave\u002Fskills\u002Ffix-review\u002FSKILL.md",[],[]]