[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A3CDMN9F47YV32P4BHGTK2":3,"skill-same:01M7A3CDMN9F47YV32P4BHGTK2":65},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7A3CDMN9F47YV32P4BHGTK2","review-doc-style",null,"Review NeMo Fabric documentation, examples, and docs-heavy changes for NVIDIA technical writing style, terminology, repository accuracy, and current public behavior. Use for documentation reviews and public-facing text changes.","leemiracle\u002Fwork4ai","leemiracle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10385913?v=4","01M79YCHARF56CHMGGTECMZN8Z","lee","01M79YCHBY9VH2CJW4P65D3DHR",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002FNeMo-Fabric\u002Frepo-docs\u002F.agents\u002Fskills\u002Freview-doc-style\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: review-doc-style\ndescription: Review NeMo Fabric documentation, examples, and docs-heavy changes for NVIDIA technical writing style, terminology, repository accuracy, and current public behavior. Use for documentation reviews and public-facing text changes.\nauthor: NVIDIA Corporation and Affiliates\nlicense: Apache-2.0\n---\n\n\n# Review Documentation Style\n\n## Companion Guidance\n\nUse `karpathy-guidelines` alongside this skill for implementation or review\nwork. Keep changes scoped, surface assumptions, and define focused validation\nbefore editing.\n\nUse this skill when reviewing docs-only changes, example-heavy changes, or any\npublic-facing text update that should be checked against NVIDIA style guidance\nand NVIDIA NeMo Fabric repo conventions.\n\n## Generated API Reference\n\n- Treat all files under `docs\u002Freference\u002Fapi\u002F` as generated output. Do not modify\n  them directly.\n- For Python API reference changes, update the source docstrings under\n  `sdk\u002Fpython\u002Fnemo-fabric-runtime\u002Fsrc\u002Fnemo_fabric\u002F` or the generator in\n  `scripts\u002Fgenerate_api_docs.sh`.\n- For Rust API reference changes, update the Rust documentation comments under\n  `crates\u002Ffabric-core\u002F` or the generator in\n  `scripts\u002Fdocs\u002Fgenerate_rust_library_reference.py`.\n- Run `just docs` to regenerate and validate the API reference after changing a\n  source or generator.\n\n## Documentation Links\n\n- For links between files under `docs\u002F`, use paths relative to the source file\n  and include the target file's `.mdx` extension. These links work in both Fern\n  builds and repository browsers.\n- Do not use Fern site-root paths such as\n  `[NeMo Fabric overview](\u002Fnemo\u002Ffabric\u002Fabout-nemo-fabric\u002Foverview)`.\n- Use the repository-relative equivalent, such as\n  `[NeMo Fabric overview](..\u002Fabout-nemo-fabric\u002Foverview.mdx)`.\n\n## Review Priorities\n\n- Prioritize factual accuracy over copy polish\n- Flag stale commands, package names, APIs, bindings, repo paths, or support claims before stylistic issues\n- Keep docs aligned with current NeMo Fabric behavior, repo layout, and entry points\n- Apply NVIDIA technical-writing guidance where it improves clarity and consistency without watering down technical precision\n- For new documentation, use `\\n` newline characters only to intentionally start a new paragraph or add space around a code block or section heading. Do not enforce a line length or reformat an entire document; apply this only to newly written text or the paragraph being edited.\n- The full product name is \"NVIDIA NeMo Fabric\".\n  - The first usage of the name (typically in the title and H1 tag) should use the full product name.\n  - All other uses of the name can use the shortened form \"NeMo Fabric\".\n  - The only acceptable usage of \"fabric\" by itself is when referring to the CLI tool, and these references must be surrounded by back-ticks.\n\n## Review Flow\n\n1. Identify the changed docs, examples, or public-facing strings.\n2. Confirm the described behavior is still true in the current repo.\n3. Check whether entry-point docs also need updates:\n   - `README.md`\n   - `docs\u002Findex.yml`\n   - Package or crate READMEs\n   - Adapter and integration READMEs such as `adapters\u002Fpython\u002Fcodex\u002FREADME.md` or `integrations\u002Fharbor\u002FREADME.md`\n4. Start with `assets\u002Fnvidia-style-guide.md`, then open only the focused support document needed for the issue under review.\n5. Scan for high-signal style issues in headings, links, code formatting, terminology, procedures, and plain-English readability.\n6. Report findings in severity order with file references and concrete rewrites.\n\n## Must-Fix Findings\n\nTreat these as blocking issues:\n\n- Commands, package names, file paths, or APIs are incorrect or stale\n- Public behavior changed but the corresponding entry-point docs were not updated\n- A doc claims support for a binding, feature, or workflow that the repo no longer provides\n- Examples or procedures are likely to fail as written\n- User-facing naming is inconsistent with current repo terminology\n- MDX top-of-file SPDX comments use HTML comment delimiters instead of\n  `{\u002F* ... *\u002F}`\n- Links between files under `docs\u002F` use Fern site-root paths instead of\n  repository-relative `.mdx` paths\n- NVIDIA is not capitalized correctly\n- Code, commands, paths, or filenames are not formatted as inline code where needed\n\n## Should-Fix Findings\n\nFlag these when they materially improve clarity or consistency:\n\n- Headings are not in title case for technical documentation\n- Code blocks, tables, or lists are introduced with incomplete lead-in sentences\n- Raw URLs or generic link text such as \"here\" appear in prose\n- Passive voice, long sentences, or vague wording bury the action\n- Terminology changes within the same document for the same concept\n- Procedures are not imperative, not parallel, or too long for one sequence\n- \"once\" is used where \"after\" is clearer\n- \"may\" is used when the meaning is possibility rather than permission and \"can\" would be clearer\n\n## High-Signal Review Checklist\n\n- **Accuracy**: Commands, paths, package names, APIs, and binding claims match the current repo.\n- **Entry points**: Top-level docs changed wherever users would naturally look first.\n- **Headings**: Technical docs use title case consistently.\n- **Voice**: Prefer active voice, present tense, short sentences, and plain English.\n- **Links**: Use descriptive anchor text, not bare URLs or weak labels. For links\n  within `docs\u002F`, use repository-relative paths with the `.mdx` extension.\n- **Formatting**: Commands, code elements, expressions, file names, and paths are monospace.\n- **MDX headers**: Top-of-file MDX SPDX comments use `{\u002F*` and `*\u002F}` delimiters.\n- **Procedures**: Steps are easy to scan, imperative, and split into smaller tasks when long.\n- **Examples**: Code blocks are introduced by full sentences and match current APIs and build commands.\n- **Terminology**: Use consistent terms throughout the document.\n- **Dates and time**: Avoid ambiguous numeric dates and ordinal dates in body text.\n- **Temporal references**: Prefer \"after\" over \"once\".\n- **Trademarks**: For learning-oriented docs, do not force trademark symbols unless the source doc explicitly requires them.\n\n## Output Format\n\nWhen performing a docs review, lead with findings and keep them actionable:\n\n- `Must fix`: incorrect, stale, misleading, or clearly noncompliant issues\n- `Should fix`: clarity and consistency issues that materially improve the doc\n- `Nice to have`: optional polish only when the review asked for thoroughness\n\nEach finding should include:\n\n- File path and line reference\n- What is wrong now\n- Why it conflicts with repo or style guidance\n- A concrete rewrite or direction\n\nIf no issues are found, say so explicitly and mention any residual risk, such as commands or examples that were not executed.\n\n## When To Open Style Support Docs\n\nStart with the checklist above and `assets\u002Fnvidia-style-guide.md`. Open support\ndocs selectively instead of reading every asset for routine reviews.\n\n| Support Doc | Open For |\n|---|---|\n| `assets\u002Fnvidia-style-technical-docs.md` | Headings, links, lists, tables, code examples, procedures, UI references, accessibility, and technical-document formatting. |\n| `assets\u002Fnvidia-style-language-mechanics.md` | Voice, tone, plain English, active voice, contractions, temporal wording, punctuation, dates, numbers, units, and symbols. |\n| `assets\u002Fnvidia-style-brand-terminology.md` | NVIDIA capitalization, product names, model names, trademarks, acronyms, titles, legal copy, SEO, and social copy. |\n\n## References\n\n- `README.md`\n- `docs\u002Findex.yml`\n- `assets\u002Fnvidia-style-guide.md`\n- `assets\u002Fnvidia-style-technical-docs.md`\n- `assets\u002Fnvidia-style-language-mechanics.md`\n- `assets\u002Fnvidia-style-brand-terminology.md`\n","# Review Documentation Style\n\n## Companion Guidance\n\nUse `karpathy-guidelines` alongside this skill for implementation or review\nwork. Keep changes scoped, surface assumptions, and define focused validation\nbefore editing.\n\nUse this skill when reviewing docs-only changes, example-heavy changes, or any\npublic-facing text update that should be checked against NVIDIA style guidance\nand NVIDIA NeMo Fabric repo conventions.\n\n## Generated API Reference\n\n- Treat all files under `docs\u002Freference\u002Fapi\u002F` as generated output. Do not modify\n  them directly.\n- For Python API reference changes, update the source docstrings under\n  `sdk\u002Fpython\u002Fnemo-fabric-runtime\u002Fsrc\u002Fnemo_fabric\u002F` or the generator in\n  `scripts\u002Fgenerate_api_docs.sh`.\n- For Rust API reference changes, update the Rust documentation comments under\n  `crates\u002Ffabric-core\u002F` or the generator in\n  `scripts\u002Fdocs\u002Fgenerate_rust_library_reference.py`.\n- Run `just docs` to regenerate and validate the API reference after changing a\n  source or generator.\n\n## Documentation Links\n\n- For links between files under `docs\u002F`, use paths relative to the source file\n  and include the target file's `.mdx` extension. These links work in both Fern\n  builds and repository browsers.\n- Do not use Fern site-root paths such as\n  `[NeMo Fabric overview](\u002Fnemo\u002Ffabric\u002Fabout-nemo-fabric\u002Foverview)`.\n- Use the repository-relative equivalent, such as\n  `[NeMo Fabric overview](..\u002Fabout-nemo-fabric\u002Foverview.mdx)`.\n\n## Review Priorities\n\n- Prioritize factual accuracy over copy polish\n- Flag stale commands, package names, APIs, bindings, repo paths, or support claims before stylistic issues\n- Keep docs aligned with current NeMo Fabric behavior, repo layout, and entry points\n- Apply NVIDIA technical-writing guidance where it improves clarity and consistency without watering down technical precision\n- For new documentation, use `\\n` newline characters only to intentionally start a new paragraph or add space around a code block or section heading. Do not enforce a line length or reformat an entire document; apply this only to newly written text or the paragraph being edited.\n- The full product name is \"NVIDIA NeMo Fabric\".\n  - The first usage of the name (typically in the title and H1 tag) should use the full product name.\n  - All other uses of the name can use the shortened form \"NeMo Fabric\".\n  - The only acceptable usage of \"fabric\" by itself is when referring to the CLI tool, and these references must be surrounded by back-ticks.\n\n## Review Flow\n\n1. Identify the changed docs, examples, or public-facing strings.\n2. Confirm the described behavior is still true in the current repo.\n3. Check whether entry-point docs also need updates:\n   - `README.md`\n   - `docs\u002Findex.yml`\n   - Package or crate READMEs\n   - Adapter and integration READMEs such as `adapters\u002Fpython\u002Fcodex\u002FREADME.md` or `integrations\u002Fharbor\u002FREADME.md`\n4. Start with `assets\u002Fnvidia-style-guide.md`, then open only the focused support document needed for the issue under review.\n5. Scan for high-signal style issues in headings, links, code formatting, terminology, procedures, and plain-English readability.\n6. Report findings in severity order with file references and concrete rewrites.\n\n## Must-Fix Findings\n\nTreat these as blocking issues:\n\n- Commands, package names, file paths, or APIs are incorrect or stale\n- Public behavior changed but the corresponding entry-point docs were not updated\n- A doc claims support for a binding, feature, or workflow that the repo no longer provides\n- Examples or procedures are likely to fail as written\n- User-facing naming is inconsistent with current repo terminology\n- MDX top-of-file SPDX comments use HTML comment delimiters instead of\n  `{\u002F* ... *\u002F}`\n- Links between files under `docs\u002F` use Fern site-root paths instead of\n  repository-relative `.mdx` paths\n- NVIDIA is not capitalized correctly\n- Code, commands, paths, or filenames are not formatted as inline code where needed\n\n## Should-Fix Findings\n\nFlag these when they materially improve clarity or consistency:\n\n- Headings are not in title case for technical documentation\n- Code blocks, tables, or lists are introduced with incomplete lead-in sentences\n- Raw URLs or generic link text such as \"here\" appear in prose\n- Passive voice, long sentences, or vague wording bury the action\n- Terminology changes within the same document for the same concept\n- Procedures are not imperative, not parallel, or too long for one sequence\n- \"once\" is used where \"after\" is clearer\n- \"may\" is used when the meaning is possibility rather than permission and \"can\" would be clearer\n\n## High-Signal Review Checklist\n\n- **Accuracy**: Commands, paths, package names, APIs, and binding claims match the current repo.\n- **Entry points**: Top-level docs changed wherever users would naturally look first.\n- **Headings**: Technical docs use title case consistently.\n- **Voice**: Prefer active voice, present tense, short sentences, and plain English.\n- **Links**: Use descriptive anchor text, not bare URLs or weak labels. For links\n  within `docs\u002F`, use repository-relative paths with the `.mdx` extension.\n- **Formatting**: Commands, code elements, expressions, file names, and paths are monospace.\n- **MDX headers**: Top-of-file MDX SPDX comments use `{\u002F*` and `*\u002F}` delimiters.\n- **Procedures**: Steps are easy to scan, imperative, and split into smaller tasks when long.\n- **Examples**: Code blocks are introduced by full sentences and match current APIs and build commands.\n- **Terminology**: Use consistent terms throughout the document.\n- **Dates and time**: Avoid ambiguous numeric dates and ordinal dates in body text.\n- **Temporal references**: Prefer \"after\" over \"once\".\n- **Trademarks**: For learning-oriented docs, do not force trademark symbols unless the source doc explicitly requires them.\n\n## Output Format\n\nWhen performing a docs review, lead with findings and keep them actionable:\n\n- `Must fix`: incorrect, stale, misleading, or clearly noncompliant issues\n- `Should fix`: clarity and consistency issues that materially improve the doc\n- `Nice to have`: optional polish only when the review asked for thoroughness\n\nEach finding should include:\n\n- File path and line reference\n- What is wrong now\n- Why it conflicts with repo or style guidance\n- A concrete rewrite or direction\n\nIf no issues are found, say so explicitly and mention any residual risk, such as commands or examples that were not executed.\n\n## When To Open Style Support Docs\n\nStart with the checklist above and `assets\u002Fnvidia-style-guide.md`. Open support\ndocs selectively instead of reading every asset for routine reviews.\n\n| Support Doc | Open For |\n|---|---|\n| `assets\u002Fnvidia-style-technical-docs.md` | Headings, links, lists, tables, code examples, procedures, UI references, accessibility, and technical-document formatting. |\n| `assets\u002Fnvidia-style-language-mechanics.md` | Voice, tone, plain English, active voice, contractions, temporal wording, punctuation, dates, numbers, units, and symbols. |\n| `assets\u002Fnvidia-style-brand-terminology.md` | NVIDIA capitalization, product names, model names, trademarks, acronyms, titles, legal copy, SEO, and social copy. |\n\n## References\n\n- `README.md`\n- `docs\u002Findex.yml`\n- `assets\u002Fnvidia-style-guide.md`\n- `assets\u002Fnvidia-style-technical-docs.md`\n- `assets\u002Fnvidia-style-language-mechanics.md`\n- `assets\u002Fnvidia-style-brand-terminology.md`\n",{"name":5,"author":24,"license":15,"description":7},"NVIDIA Corporation and Affiliates","main","ffa016d3c9a8d32821f71f6d9d916c30e04fcb67","讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002FNeMo-Fabric\u002Frepo-docs\u002F.agents\u002Fskills\u002Freview-doc-style",0,"https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai","https:\u002F\u002Fgithub.com\u002Fleemiracle","i have some experience that make me better, so i want more. follow and star me would be a good choice.","2026-11-12 17:16:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add leemiracle\u002Fwork4ai --skill review-doc-style",{"tool":39,"command":40},"bunx","bunx skills add leemiracle\u002Fwork4ai --skill review-doc-style",{"tool":42,"command":43},"pnpm","pnpm dlx skills add leemiracle\u002Fwork4ai --skill review-doc-style","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002FNeMo-Fabric\u002Frepo-docs\u002F.agents\u002Fskills\u002Freview-doc-style\u002FSKILL.md",true,[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"assets\u002Fnvidia-style-brand-terminology.md","ASSET","资产文件",3864,"https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002FNeMo-Fabric\u002Frepo-docs\u002F.agents\u002Fskills\u002Freview-doc-style\u002Fassets\u002Fnvidia-style-brand-terminology.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"assets\u002Fnvidia-style-guide.md",5388,"https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002FNeMo-Fabric\u002Frepo-docs\u002F.agents\u002Fskills\u002Freview-doc-style\u002Fassets\u002Fnvidia-style-guide.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"assets\u002Fnvidia-style-language-mechanics.md",6984,"https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002FNeMo-Fabric\u002Frepo-docs\u002F.agents\u002Fskills\u002Freview-doc-style\u002Fassets\u002Fnvidia-style-language-mechanics.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"assets\u002Fnvidia-style-technical-docs.md",5851,"https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002FNeMo-Fabric\u002Frepo-docs\u002F.agents\u002Fskills\u002Freview-doc-style\u002Fassets\u002Fnvidia-style-technical-docs.md",[66,73,80,87,94,101],{"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},"01M7A57J4E78QJZS8MA72P82DV","agentic-ecology-ui","Guidelines and templates for creating a generic web UI to visualize, rank, filter, and annotate vector databases. The UI has a hierarchical structure covering database selection, label selection\u002Fdefinition, ranking\u002Ffiltering configuration, and row visualization\u002Fannotation. Use when building, serving, or adapting an interactive web UI for Hoplite vector databases.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透google-deepmind\u002Fagentic_ecology\u002Frepo-docs\u002Fskills\u002Fagentic-ecology-ui\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},"01M7A57C4RGS1A7VM6CNPNQDBH","agentic-ecology-init","Initializes a local uv-managed project directory for agentic ecology workloads. Sets up Python dependencies using reference pyproject.toml and uv.lock, configures workspace rules, and ensures Agentic Ecology skills are discoverable. Use when initializing a new project workspace or bootstrapping a clean environment.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透google-deepmind\u002Fagentic_ecology\u002Frepo-docs\u002Fskills\u002Fagentic-ecology-init\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":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7A576Q1GYF5GAQCWGPPDQWZ","agentic-ecology-camera-traps","Provides capabilities to run SpeciesNet detector and classifier on camera trap images, extract crop-level feature embeddings, and populate a Hoplite vector database for downstream search and agile modeling. Use when ingesting camera trap images, classifying wildlife photos, or indexing camera trap data.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透google-deepmind\u002Fagentic_ecology\u002Frepo-docs\u002Fskills\u002Fagentic-ecology-camera-traps\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7A5708M54MMTKXQARDCJQMW","agentic-ecology-bioacoustics","Provides bioacoustic analysis capabilities for ecologists and researchers using the perch-hoplite Python package. A typical use case is to use agile modeling to bootstrap the creation and deployment of a bespoke detector for targeted species on an existing collection of passive acoustic monitoring recordings. Use when processing and annotating audio recordings for bioacoustic applications.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透google-deepmind\u002Fagentic_ecology\u002Frepo-docs\u002Fskills\u002Fagentic-ecology-bioacoustics\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7A53GYCZY3AT9C2FR44TC35","sample-skill","Sample skill used by agent-env integration tests. Exercises SKILL.md parsing plus supporting scripts and references.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透browser-use\u002Fagentenv-framework\u002Frepo-docs\u002Ftst\u002Fdata\u002Fskills\u002Fsample_skill\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7A4KD50DHSNH1SCNKP1J6S1","simready-foundation-validate-foundation-change","Use for auditing SimReady requirement, validator, feature, profile, adapter, test, and skill consistency.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fsimready-foundation\u002Frepo-docs\u002F.codex\u002Fskills\u002Fsimready-foundation-validate-foundation-change\u002FSKILL.md",[],[]]