[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C0PC4MHYP5WNFBZ9BVBZJX":3,"skill-same:01M6C0PC4MHYP5WNFBZ9BVBZJX":76},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6C0PC4MHYP5WNFBZ9BVBZJX","ontology-scout",null,"Searches for and evaluates reusable ontological resources. Queries OLS, BioPortal, OBO Foundry, and LOV. Extracts ontology modules via ROBOT. Finds applicable Ontology Design Patterns. Use when looking for existing ontologies to reuse or align with.","beep-effect\u002Fbeep-effect","beep-effect","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F293012014?v=4","01M6C0KM5WSBFT39QDNXKH1JVY","Beep Effect","01M6C0KM9QBN9R26F3EHTSWR14",80,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbeep-effect\u002Fbeep-effect\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fontology-scout\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"ontology scout","scout","ontology","patterns","when","Existing","for","with","reuse","resources","via","robot","align","design","queries","reusable","design patterns","modules","use","foundry","2026-11-10 10:12:30",false,"---\nname: ontology-scout\ndescription: >\n  Searches for and evaluates reusable ontological resources. Queries\n  OLS, BioPortal, OBO Foundry, and LOV. Extracts ontology modules via\n  ROBOT. Finds applicable Ontology Design Patterns. Use when looking\n  for existing ontologies to reuse or align with.\n---\n\n# Ontology Scout (Reuse Advisor)\n\n## Role Statement\n\nYou are responsible for the knowledge acquisition phase — specifically,\ndiscovering and evaluating existing ontological resources before building\nfrom scratch. You search registries, evaluate candidate ontologies for\nquality and coverage, recommend reuse strategies, and extract modules via\nROBOT. You do NOT create new classes or axioms — that is the work of\ndownstream skills.\n\n## When to Activate\n\n- User wants to find existing ontologies covering their domain\n- User mentions \"reuse\", \"import\", \"alignment\", or \"existing ontology\"\n- Starting conceptualization (always check what exists first)\n- Pipeline A Step 2 or Pipeline B Step 1\n\n## Shared Reference Materials\n\nRead these files from `_shared\u002F` before beginning work:\n\n- `_shared\u002Fmethodology-backbone.md` — lifecycle phase context (Phase 2: Knowledge Acquisition)\n- `_shared\u002Fbfo-categories.md` — needed to evaluate BFO alignment of candidates\n- `_shared\u002Fnaming-conventions.md` — to assess naming quality of candidates\n- `_shared\u002Fnamespaces.json` — standard prefixes for search queries\n\n## Core Workflow\n\n### Always-Reuse Baseline\n\nBefore domain-specific search, assume these foundational ontologies are\nin-scope unless there is a project-specific reason not to use them:\n\n- **Dublin Core Terms (`dcterms`)**: common metadata fields\n- **SKOS**: concept labeling and lexical organization\n- **PROV-O**: provenance and derivation modeling\n- **FOAF or schema.org**: people\u002Forganization basics\n\nDocument baseline reuse decisions in the reuse report before evaluating\ndomain ontologies.\n\n### Step 1: Search Registries\n\nFor each candidate term from the pre-glossary, search multiple registries:\n\n```bash\n# Search via oaklib (OLS backend)\nuv run runoak -i ols: search \"TERM\"\n\n# Search via oaklib (BioPortal backend, if API key configured)\nuv run runoak -i bioportal: search \"TERM\"\n\n# Search OBO Foundry ontologies specifically\nuv run runoak -i sqlite:obo:{ontology_id} search \"TERM\"\n```\n\nAlso check specialized repositories when relevant:\n- OMG specifications catalog\n- COLORE repository\n- Schema.org vocabulary docs\n- IBC AgroPortal\n- Google Dataset Search (for ontology-linked datasets)\n\n### Step 2: Evaluate Candidates\n\nScore each candidate ontology on nine dimensions:\n\n| Criterion | Weight | How to Assess |\n|-----------|--------|--------------|\n| Coverage | High | % of pre-glossary terms found in the ontology |\n| Quality | High | OBO Dashboard score, label\u002Fdefinition coverage, ROBOT report |\n| License | Required | Must be open (CC-BY or CC0 preferred) |\n| Community | Medium | Active maintenance, GitHub activity, publications |\n| BFO Alignment | Medium | Already aligned to BFO? Uses RO relations? |\n| Syntactic correctness | Required | `robot validate --input candidate.owl` |\n| Logical consistency | Required | `robot reason --reasoner ELK --input candidate.owl` |\n| Modularization | Medium | Can modules be imported independently? |\n| Metadata completeness | Medium | `robot report --input candidate.owl` + header metadata checks |\n\nEven when a candidate is not reusable, keep it as a benchmark reference for\ncoverage and modeling comparison.\n\n### Step 3: Reuse Decision\n\nApply the NeOn reuse decision tree:\n\n| Coverage | Strategy | Tool |\n|----------|----------|------|\n| >80% of needs | Direct Import | `owl:imports` |\n| 40-80% | Module Extraction | `robot extract` |\n| \u003C40% but has useful terms | MIREOT (term borrowing) | `robot extract --method MIREOT` |\n| Good structure, wrong domain | ODP Reuse | Instantiate design pattern |\n| Related ontology exists | SSSOM Mapping | Defer to `ontology-mapper` |\n\n#### CQ Benchmark Probe\n\nRun representative competency-question probes against each short-listed\ncandidate (or extracted module) to test practical fit:\n\n- Select 3-5 high-priority CQs from requirements.\n- Draft quick probe queries (or adapt existing CQ drafts).\n- Record whether the candidate can answer each probe fully, partially, or not\n  at all.\n\n### Step 4: Module Extraction\n\n#### Extraction Method Trade-offs\n\n| Method | What It Extracts | Best For | Watch Out |\n|--------|-----------------|----------|-----------|\n| MIREOT | Term + ancestors only | Large ontologies (GO, ChEBI) — fast, minimal | Loses sibling context and some axioms |\n| STAR | All axioms involving the term | Small\u002Fmedium ontologies — most complete | Can pull in unexpected classes via axiom references |\n| BOT | Term + all ancestors (bottom module) | Good middle ground | May include more than needed for deep hierarchies |\n| TOP | Term + all descendants (top module) | Extracting a subtree | Large result if term has many descendants |\n\n**Import management pitfalls**:\n- **Transitive import chains**: Importing one OBO ontology can pull in dozens\n  of transitive imports. Check what you are actually loading.\n- **Import freshness**: Upstream ontologies release on their own schedule. Pin\n  versions and use a refresh workflow (see curator skill).\n- **Circular imports**: Occasionally A imports B imports C imports A. This\n  causes reasoner failures. Check for cycles before committing.\n- **Stale term files**: The `*_terms.txt` pattern (one IRI per line) breaks\n  silently if a term has been obsoleted upstream. Validate term existence\n  during import refresh.\n\nFor recommended imports:\n\n```bash\n# Create term list file\necho \"http:\u002F\u002Fpurl.obolibrary.org\u002Fobo\u002FGO_0008150\" > imports\u002Fgo_terms.txt\necho \"http:\u002F\u002Fpurl.obolibrary.org\u002Fobo\u002FGO_0003674\" >> imports\u002Fgo_terms.txt\n\n# Extract module (STAR method — most complete)\nrobot extract --method STAR \\\n  --input-iri http:\u002F\u002Fpurl.obolibrary.org\u002Fobo\u002Fgo.owl \\\n  --term-file imports\u002Fgo_terms.txt \\\n  --output imports\u002Fgo_import.owl\n\n# Extract module (MIREOT — minimal, just term + parents)\nrobot extract --method MIREOT \\\n  --input-iri http:\u002F\u002Fpurl.obolibrary.org\u002Fobo\u002Fgo.owl \\\n  --term-file imports\u002Fgo_terms.txt \\\n  --output imports\u002Fgo_import.owl\n```\n\n### Step 5: ODP Search\n\nSearch for applicable Ontology Design Patterns:\n\n- **Part-Whole**: Modeling mereological relationships\n- **N-ary Relation**: Relations with >2 participants\n- **Value Partition**: Quality values as controlled vocabularies\n- **Participation**: Continuant participation in processes\n- **Information Realization**: GDC\u002FICE patterns\n- **Role**: Social\u002Fcontextual properties\n\nDocument which ODPs apply and how they should be instantiated.\n\n## Tool Commands\n\n### Registry search\n\n```bash\n# OLS search with result limit\nuv run runoak -i ols: search \"musical instrument\" -l 20\n\n# Get term details from a specific ontology\nuv run runoak -i sqlite:obo:go info GO:0008150\n\n# Get ancestors of a term\nuv run runoak -i sqlite:obo:go ancestors GO:0008150\n\n# Check if ontology is in OBO Foundry\nuv run runoak -i obo: ontologies\n```\n\n### ROBOT extraction\n\n```bash\n# BOT extraction (bottom module — term + all ancestors)\nrobot extract --method BOT \\\n  --input source.owl \\\n  --term \"http:\u002F\u002Fexample.org\u002FTerm\" \\\n  --output module.owl\n\n# TOP extraction (top module — term + all descendants)\nrobot extract --method TOP \\\n  --input source.owl \\\n  --term \"http:\u002F\u002Fexample.org\u002FTerm\" \\\n  --output module.owl\n```\n\n### Quality assessment of candidate\n\n```bash\n# Syntax validation\nrobot validate --input candidate.owl\n\n# Logical consistency\nrobot reason --reasoner ELK --input candidate.owl\n\n# Run ROBOT report on candidate ontology\nrobot report --input candidate.owl --output candidate-report.tsv\n\n# Check label coverage\nuv run runoak -i candidate.owl statistics\n\n# Run representative CQ probes (if available)\nrobot verify --input candidate.owl --queries ontologies\u002F{name}\u002Ftests\u002Fcandidate-probes\u002F\n```\n\n## Outputs\n\nThis skill produces:\n\n| Artifact | Location | Format | Description |\n|----------|----------|--------|-------------|\n| Reuse report | `ontologies\u002F{name}\u002Fdocs\u002Freuse-report.md` | Markdown | Scored candidate ontologies with recommendations |\n| Import term lists | `imports\u002F{source}_terms.txt` | Text (one IRI per line) | Terms to extract from each source |\n| Extracted modules | `imports\u002F{source}_import.owl` | OWL\u002FXML | ROBOT-extracted modules |\n| ODP recommendations | `ontologies\u002F{name}\u002Fdocs\u002Fodp-recommendations.md` | Markdown | Applicable design patterns with instantiation guidance |\n\n## Handoff\n\n**Receives from**: `ontology-requirements` — `ontologies\u002F{name}\u002Fdocs\u002Fpre-glossary.csv`, `ontologies\u002F{name}\u002Fdocs\u002Fscope.md`\n\n**Passes to**:\n- `ontology-foundational-auditor` — reuse report, import term lists, ODP recommendations (the auditor's reuse pass consumes these; the conceptualizer receives only ratified results downstream)\n- `ontology-mapper` (Pipeline B) — target ontology identifiers, reuse recommendations\n\n**Handoff checklist**:\n- [ ] Every pre-glossary term has been searched in at least one registry\n- [ ] Reuse report includes scored candidates with clear recommendations\n- [ ] Extracted modules load without errors (`robot validate`)\n- [ ] ODP recommendations reference specific pattern templates\n\n## Anti-Patterns to Avoid\n\n- **Not-invented-here syndrome**: Always search before creating new terms.\n  Reuse is preferred over reinvention.\n- **Uncritical reuse**: Don't import entire large ontologies (e.g., all of\n  GO) when only a handful of terms are needed. Use module extraction.\n- **License violations**: Never recommend importing ontologies with\n  incompatible licenses.\n- **Stale sources**: Check that candidate ontologies are actively maintained.\n  An unmaintained ontology is a liability.\n\n## Error Handling\n\n| Error | Likely Cause | Recovery |\n|-------|-------------|----------|\n| OLS API unreachable | Network issue or rate limit | Retry with backoff; fall back to local SQLite cache |\n| ROBOT extract fails | Invalid IRI or unreachable source | Download ontology locally first, then extract |\n| No candidates found | Domain is niche or uses non-standard terminology | Broaden search terms; try synonyms from pre-glossary |\n| Candidate has no license | License not declared in metadata | Contact maintainers or choose alternatives |\n","# Ontology Scout (Reuse Advisor)\n\n## Role Statement\n\nYou are responsible for the knowledge acquisition phase — specifically,\ndiscovering and evaluating existing ontological resources before building\nfrom scratch. You search registries, evaluate candidate ontologies for\nquality and coverage, recommend reuse strategies, and extract modules via\nROBOT. You do NOT create new classes or axioms — that is the work of\ndownstream skills.\n\n## When to Activate\n\n- User wants to find existing ontologies covering their domain\n- User mentions \"reuse\", \"import\", \"alignment\", or \"existing ontology\"\n- Starting conceptualization (always check what exists first)\n- Pipeline A Step 2 or Pipeline B Step 1\n\n## Shared Reference Materials\n\nRead these files from `_shared\u002F` before beginning work:\n\n- `_shared\u002Fmethodology-backbone.md` — lifecycle phase context (Phase 2: Knowledge Acquisition)\n- `_shared\u002Fbfo-categories.md` — needed to evaluate BFO alignment of candidates\n- `_shared\u002Fnaming-conventions.md` — to assess naming quality of candidates\n- `_shared\u002Fnamespaces.json` — standard prefixes for search queries\n\n## Core Workflow\n\n### Always-Reuse Baseline\n\nBefore domain-specific search, assume these foundational ontologies are\nin-scope unless there is a project-specific reason not to use them:\n\n- **Dublin Core Terms (`dcterms`)**: common metadata fields\n- **SKOS**: concept labeling and lexical organization\n- **PROV-O**: provenance and derivation modeling\n- **FOAF or schema.org**: people\u002Forganization basics\n\nDocument baseline reuse decisions in the reuse report before evaluating\ndomain ontologies.\n\n### Step 1: Search Registries\n\nFor each candidate term from the pre-glossary, search multiple registries:\n\n```bash\n# Search via oaklib (OLS backend)\nuv run runoak -i ols: search \"TERM\"\n\n# Search via oaklib (BioPortal backend, if API key configured)\nuv run runoak -i bioportal: search \"TERM\"\n\n# Search OBO Foundry ontologies specifically\nuv run runoak -i sqlite:obo:{ontology_id} search \"TERM\"\n```\n\nAlso check specialized repositories when relevant:\n- OMG specifications catalog\n- COLORE repository\n- Schema.org vocabulary docs\n- IBC AgroPortal\n- Google Dataset Search (for ontology-linked datasets)\n\n### Step 2: Evaluate Candidates\n\nScore each candidate ontology on nine dimensions:\n\n| Criterion | Weight | How to Assess |\n|-----------|--------|--------------|\n| Coverage | High | % of pre-glossary terms found in the ontology |\n| Quality | High | OBO Dashboard score, label\u002Fdefinition coverage, ROBOT report |\n| License | Required | Must be open (CC-BY or CC0 preferred) |\n| Community | Medium | Active maintenance, GitHub activity, publications |\n| BFO Alignment | Medium | Already aligned to BFO? Uses RO relations? |\n| Syntactic correctness | Required | `robot validate --input candidate.owl` |\n| Logical consistency | Required | `robot reason --reasoner ELK --input candidate.owl` |\n| Modularization | Medium | Can modules be imported independently? |\n| Metadata completeness | Medium | `robot report --input candidate.owl` + header metadata checks |\n\nEven when a candidate is not reusable, keep it as a benchmark reference for\ncoverage and modeling comparison.\n\n### Step 3: Reuse Decision\n\nApply the NeOn reuse decision tree:\n\n| Coverage | Strategy | Tool |\n|----------|----------|------|\n| >80% of needs | Direct Import | `owl:imports` |\n| 40-80% | Module Extraction | `robot extract` |\n| \u003C40% but has useful terms | MIREOT (term borrowing) | `robot extract --method MIREOT` |\n| Good structure, wrong domain | ODP Reuse | Instantiate design pattern |\n| Related ontology exists | SSSOM Mapping | Defer to `ontology-mapper` |\n\n#### CQ Benchmark Probe\n\nRun representative competency-question probes against each short-listed\ncandidate (or extracted module) to test practical fit:\n\n- Select 3-5 high-priority CQs from requirements.\n- Draft quick probe queries (or adapt existing CQ drafts).\n- Record whether the candidate can answer each probe fully, partially, or not\n  at all.\n\n### Step 4: Module Extraction\n\n#### Extraction Method Trade-offs\n\n| Method | What It Extracts | Best For | Watch Out |\n|--------|-----------------|----------|-----------|\n| MIREOT | Term + ancestors only | Large ontologies (GO, ChEBI) — fast, minimal | Loses sibling context and some axioms |\n| STAR | All axioms involving the term | Small\u002Fmedium ontologies — most complete | Can pull in unexpected classes via axiom references |\n| BOT | Term + all ancestors (bottom module) | Good middle ground | May include more than needed for deep hierarchies |\n| TOP | Term + all descendants (top module) | Extracting a subtree | Large result if term has many descendants |\n\n**Import management pitfalls**:\n- **Transitive import chains**: Importing one OBO ontology can pull in dozens\n  of transitive imports. Check what you are actually loading.\n- **Import freshness**: Upstream ontologies release on their own schedule. Pin\n  versions and use a refresh workflow (see curator skill).\n- **Circular imports**: Occasionally A imports B imports C imports A. This\n  causes reasoner failures. Check for cycles before committing.\n- **Stale term files**: The `*_terms.txt` pattern (one IRI per line) breaks\n  silently if a term has been obsoleted upstream. Validate term existence\n  during import refresh.\n\nFor recommended imports:\n\n```bash\n# Create term list file\necho \"http:\u002F\u002Fpurl.obolibrary.org\u002Fobo\u002FGO_0008150\" > imports\u002Fgo_terms.txt\necho \"http:\u002F\u002Fpurl.obolibrary.org\u002Fobo\u002FGO_0003674\" >> imports\u002Fgo_terms.txt\n\n# Extract module (STAR method — most complete)\nrobot extract --method STAR \\\n  --input-iri http:\u002F\u002Fpurl.obolibrary.org\u002Fobo\u002Fgo.owl \\\n  --term-file imports\u002Fgo_terms.txt \\\n  --output imports\u002Fgo_import.owl\n\n# Extract module (MIREOT — minimal, just term + parents)\nrobot extract --method MIREOT \\\n  --input-iri http:\u002F\u002Fpurl.obolibrary.org\u002Fobo\u002Fgo.owl \\\n  --term-file imports\u002Fgo_terms.txt \\\n  --output imports\u002Fgo_import.owl\n```\n\n### Step 5: ODP Search\n\nSearch for applicable Ontology Design Patterns:\n\n- **Part-Whole**: Modeling mereological relationships\n- **N-ary Relation**: Relations with >2 participants\n- **Value Partition**: Quality values as controlled vocabularies\n- **Participation**: Continuant participation in processes\n- **Information Realization**: GDC\u002FICE patterns\n- **Role**: Social\u002Fcontextual properties\n\nDocument which ODPs apply and how they should be instantiated.\n\n## Tool Commands\n\n### Registry search\n\n```bash\n# OLS search with result limit\nuv run runoak -i ols: search \"musical instrument\" -l 20\n\n# Get term details from a specific ontology\nuv run runoak -i sqlite:obo:go info GO:0008150\n\n# Get ancestors of a term\nuv run runoak -i sqlite:obo:go ancestors GO:0008150\n\n# Check if ontology is in OBO Foundry\nuv run runoak -i obo: ontologies\n```\n\n### ROBOT extraction\n\n```bash\n# BOT extraction (bottom module — term + all ancestors)\nrobot extract --method BOT \\\n  --input source.owl \\\n  --term \"http:\u002F\u002Fexample.org\u002FTerm\" \\\n  --output module.owl\n\n# TOP extraction (top module — term + all descendants)\nrobot extract --method TOP \\\n  --input source.owl \\\n  --term \"http:\u002F\u002Fexample.org\u002FTerm\" \\\n  --output module.owl\n```\n\n### Quality assessment of candidate\n\n```bash\n# Syntax validation\nrobot validate --input candidate.owl\n\n# Logical consistency\nrobot reason --reasoner ELK --input candidate.owl\n\n# Run ROBOT report on candidate ontology\nrobot report --input candidate.owl --output candidate-report.tsv\n\n# Check label coverage\nuv run runoak -i candidate.owl statistics\n\n# Run representative CQ probes (if available)\nrobot verify --input candidate.owl --queries ontologies\u002F{name}\u002Ftests\u002Fcandidate-probes\u002F\n```\n\n## Outputs\n\nThis skill produces:\n\n| Artifact | Location | Format | Description |\n|----------|----------|--------|-------------|\n| Reuse report | `ontologies\u002F{name}\u002Fdocs\u002Freuse-report.md` | Markdown | Scored candidate ontologies with recommendations |\n| Import term lists | `imports\u002F{source}_terms.txt` | Text (one IRI per line) | Terms to extract from each source |\n| Extracted modules | `imports\u002F{source}_import.owl` | OWL\u002FXML | ROBOT-extracted modules |\n| ODP recommendations | `ontologies\u002F{name}\u002Fdocs\u002Fodp-recommendations.md` | Markdown | Applicable design patterns with instantiation guidance |\n\n## Handoff\n\n**Receives from**: `ontology-requirements` — `ontologies\u002F{name}\u002Fdocs\u002Fpre-glossary.csv`, `ontologies\u002F{name}\u002Fdocs\u002Fscope.md`\n\n**Passes to**:\n- `ontology-foundational-auditor` — reuse report, import term lists, ODP recommendations (the auditor's reuse pass consumes these; the conceptualizer receives only ratified results downstream)\n- `ontology-mapper` (Pipeline B) — target ontology identifiers, reuse recommendations\n\n**Handoff checklist**:\n- [ ] Every pre-glossary term has been searched in at least one registry\n- [ ] Reuse report includes scored candidates with clear recommendations\n- [ ] Extracted modules load without errors (`robot validate`)\n- [ ] ODP recommendations reference specific pattern templates\n\n## Anti-Patterns to Avoid\n\n- **Not-invented-here syndrome**: Always search before creating new terms.\n  Reuse is preferred over reinvention.\n- **Uncritical reuse**: Don't import entire large ontologies (e.g., all of\n  GO) when only a handful of terms are needed. Use module extraction.\n- **License violations**: Never recommend importing ontologies with\n  incompatible licenses.\n- **Stale sources**: Check that candidate ontologies are actively maintained.\n  An unmaintained ontology is a liability.\n\n## Error Handling\n\n| Error | Likely Cause | Recovery |\n|-------|-------------|----------|\n| OLS API unreachable | Network issue or rate limit | Retry with backoff; fall back to local SQLite cache |\n| ROBOT extract fails | Invalid IRI or unreachable source | Download ontology locally first, then extract |\n| No candidates found | Domain is niche or uses non-standard terminology | Broaden search terms; try synonyms from pre-glossary |\n| Candidate has no license | License not declared in metadata | Contact maintainers or choose alternatives |\n",{"name":5,"description":7},"main","467b9e7e2ed4a0696bb52a7c883c388282061610",".claude\u002Fskills\u002Fontology-scout",14,"https:\u002F\u002Fgithub.com\u002Fbeep-effect\u002Fbeep-effect","https:\u002F\u002Fwww.oip.law","https:\u002F\u002Fgithub.com\u002Fbeep-effect","2026-11-10 15:59:29",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add beep-effect\u002Fbeep-effect --skill ontology-scout",{"tool":68,"command":69},"bunx","bunx skills add beep-effect\u002Fbeep-effect --skill ontology-scout",{"tool":71,"command":72},"pnpm","pnpm dlx skills add beep-effect\u002Fbeep-effect --skill ontology-scout","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbeep-effect\u002Fbeep-effect\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fontology-scout\u002FSKILL.md",true,[],[77,103,113,123,158,183],{"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":49},"01M714DQT4JQHZ11X0RH0T8RQ7","auth-environments","Sign Claude Code in to a chosen Claude subscription on every linked T3 fleet host (grok-bot, beep-worker, dankserver, tbk-worker, tom-pc-1-wsl). Use when a Claude account hits its weekly limit, when `bun run beep accounts` shows the fleet's account used up, or on `\u002Fauth-environments`. Opens each host's OAuth page and a masked KDE code dialog together and verifies the admitted account.","https:\u002F\u002Fgithub.com\u002Fbeep-effect\u002Fbeep-effect\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fauth-environments\u002FSKILL.md",[],[84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,33],"auth","environments","auth environments","path","limit","page","python","canonical","dialog","fleet","run","active","weekly","bot","workstation","up","worker","host","code",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":49},"01M6C0RK94T5QGSZ0K9TA5Q2EF","shadcn","Fixture for immutable shadcn skill provenance.","https:\u002F\u002Fgithub.com\u002Fbeep-effect\u002Fbeep-effect\u002Fblob\u002Fmain\u002Fpackages\u002Ftooling\u002Ftool\u002Fcli\u002Ftest\u002Ffixtures\u002Fskills-provenance\u002Fshadcn\u002Fupstream\u002FSKILL.md",[],[105,110,111,112,35],"immutable","provenance","fixture",{"skillNo":114,"name":115,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":49},"01M6C0RGPWMYM5KS62ZZPNAZ0W","qa-inventory-judge","https:\u002F\u002Fgithub.com\u002Fbeep-effect\u002Fbeep-effect\u002Fblob\u002Fmain\u002Fpackages\u002Ftooling\u002Ftool\u002Fcli\u002Fskills\u002Fqa-inventory-judge\u002FSKILL.md",[],[119,120,121,122],"inventory","qa","qa inventory judge","judge",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":127,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":133,"publishedAt":49},"01M6C0RDVR0A6W6ZJCJMEYJT77","practice-onboarding","Set up a lawyer's computer for their practice through the practice gateway. Use when the lawyer asks to get set up, to connect their documents, mail, calendar or practice tools, or when the practice gateway reports that setup is incomplete. Interviews the lawyer one question at a time, saves a practice profile, then checks and repairs the computer until setup is complete.","MIT","https:\u002F\u002Fgithub.com\u002Fbeep-effect\u002Fbeep-effect\u002Fblob\u002Fmain\u002Fapps\u002Fpractice-gateway\u002Fplugin\u002Fskills\u002Fpractice-onboarding\u002FSKILL.md",[130],{"categoryNo":131,"categoryName":132,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源",[134,135,136,137,138,139,140,141,33,99,142,143,144,145,146,147,148,149,150,151,102,152,153,154,155,156,157],"onboarding","practice onboarding","at","guide","interviews","calendar","mail","reports","time","get","save","question","profile","Tools","setup","beep","status","desktop","documents","connect","computer","windows","gateway","SET",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":167,"publishedAt":49},"01M6C0RB09NRJN0E1W3ND9HDE6","triage-nda","Screen NDAs before inventor disclosures or client pitches at Oppold IP Law. Flag disclosure, residuals, marking, term, and hidden IP rights for attorney review.","https:\u002F\u002Fgithub.com\u002Fbeep-effect\u002Fbeep-effect\u002Fblob\u002Fmain\u002Fapps\u002Fpractice-claude-mod\u002Fskills\u002Ftriage-nda\u002FSKILL.md",[164],{"categoryNo":165,"categoryName":166,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[168,169,170,171,172,173,174,175,176,177,136,178,179,180,181,182,35],"nda","triage","triage nda","2026","screen","ip","plugins","work","review","knowledge","knowledge-work","legal","client","hidden","rights",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":190,"publishedAt":49},"01M6C0R8B5D35H50QY426AYR39","review-contract","Review IP agreements for Oppold IP Law. Use for assignments, licenses, inventor agreements, joint development, or NDAs involving inventions. Prepare cited issues and proposed revisions for attorney review.","https:\u002F\u002Fgithub.com\u002Fbeep-effect\u002Fbeep-effect\u002Fblob\u002Fmain\u002Fapps\u002Fpractice-claude-mod\u002Fskills\u002Freview-contract\u002FSKILL.md",[189],{"categoryNo":165,"categoryName":166,"taxonomyType":26,"taxonomyTypeDesc":27},[176,191,192,171,178,179,47,173,35,193,174,175,177,194,195],"review contract","contract","prepare","issues","development"]