LydiaTools/skill-bundle-check

Última atividade de origem registrada: 31 de outubro de 2026 às 15:10

Catálogo do SkillsMP atualizado: 9 de novembro de 2026 às 14:22

skills coletadas: 4

Estrelas no GitHub: 0
Forks no GitHub: 0

Instalar com um assistente de IA

Copie este prompt para o assistente de IA que você usa.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/LydiaTools/skill-bundle-check.

README do repositório

Arquivo de origem do README: README.md

Ler o README original

Expandir README completo

# Skill Bundle Check **Your skill works in the repo. Does it still work after installation?** [Compare Skill folders online](https://lydiatools.github.io/skill-bundle-check/web/diff.html) · [Review Markdown tables](https://lydiatools.github.io/skill-bundle-check/web/) · [Download v0.15.0](https://github.com/LydiaTools/skill-bundle-check/releases/tag/v0.15.0) · [中文说明](README.zh-CN.md) Using a Skill inside a plugin? [Check the surrounding plugin files](#plugin-tree). Not sure where a Skill was installed or whether its copy changed? [Follow the practical checklist](docs/where-is-my-skill.md). Uploading one Skill as a ZIP? [Review its structure in your browser](https://lydiatools.github.io/skill-bundle-check/web/zip.html) or [use Python](#review-a-single-skill-zip). [![Example Skill ZIP folder layout beside the actual checker's hint for a fictional ZIP](docs/assets/skill-zip-guide-en.png)](https://lydiatools.github.io/skill-bundle-check/web/zip.html) *A folder-layout illustration beside a real checker result for a fictional ZIP. Click to try the ZIP review.* Installing a same-name Skill? [Check the destination first](#check-a-destination-before-installing). Skill Bundle Check provides read-only checks. `check` verifies that local references from a source Agent Skill are present and resolve in the folder produced by your installer or release build. It does not compare file contents or attest package integrity. `check-agent` looks for `SKILL.md` in a supported agent's documented install directory; `--agent all` checks every built-in profile in one pass and shows copies found at other known roots. `doctor` scans the immediate Skill entries in one or more selected roots for missing or broken `SKILL.md` paths. `snapshot` and `compare` show presence changes across explicitly selected installation roots. `diff` compares two Skill folders; `diff-tree` compares larger selected directory trees, including plugin files outside a Skill folder. `review-pipes` points out certain Markdown table escapes; `review-shell` highlights selected script paths in shell examples. Both provide hints for human review. The [v0.15.0 release](https://github.com/LydiaTools/skill-bundle-check/releases/tag/v0.15.0) includes the current CLI commands, including `doctor` and the all-agent location report. It does not run the skill, start the agent, or claim that the agent loaded it at runtime. ## Why this exists People have reported Agent Skills whose `SKILL.md` points to files that are missing or unreachable after installation. This shows up in different forms: - [Agent-Reach](https://github.com/Panniantong/Agent-Reach/issues/622), [Hallmark](https://github.com/Nutlope/hallmark/issues/76), and [Tastemaker](https://github.com/codeswithroh/tastemaker/issues/86) report installations or conversions that leave referenced resources unavailable. - [Addy Osmani's agent-skills #468](https://github.com/addyosmani/agent-skills/issues/468) reported shared references that did not resolve even in a full plugin install; [#469](https://github.com/addyosmani/agent-skills/pull/469) fixed those links. [#597](https://github.com/addyosmani/agent-skills/issues/597) reports a separate single-skill installation case. See the [reproducible single-Skill installation case](docs/case-single-skill-install.md). - [OpenAI Codex #8364](https://github.com/openai/codex/issues/8364) reports an agent sometimes failing to find a referenced script; the maintainer linked it to a separate issue. The report does not establish that the installed script itself was missing. - [CLI-Anything #331](https://github.com/HKUDS/CLI-Anything/issues/331) reports an installer that copies the skill but leaves its referenced methodology files behind. - [Vercel Skills #1851](https://github.com/vercel-labs/skills/issues/1851) reports a successful global install that places a Skill in a shared directory instead of Antigravity CLI's documented global directory. - [Vercel Skills #537](https://github.com/vercel-labs/skills/issues/537) reports a global install that leaves an agent-specific directory unlinked; a one-pass profile report can show which documented paths contain the Skill. - [Vercel Skills #456](https://github.com/vercel-labs/skills/issues/456) describes relative Skill links that can break when an installed `skills` directory is itself a symlink. One report describes 58 broken links after a global install. `doctor` can surface broken Skill-directory links and missing `SKILL.md` paths in selected roots; it does not repair them or determine whether an agent loaded the Skill. Format validation alone may not catch these failures. A [reproduction report](https://tinkerhood.com/learn/skill-references-and-assets/) shows a skill-reference check passing while the referenced file is missing. This tool checks the actual source and installed folders instead. See also a [real generated-guide link case](docs/case-generated-rule-links.md). Related but outside this check: [Codex #28505](https://github.com/openai/codex/issues/28505) reports a valid personal Skill on disk that does not appear in the desktop picker. A path report can narrow down placement, but cannot diagnose or repair runtime indexing. [Microsoft APM #2966](https://github.com/microsoft/apm/issues/2966) reports a resource that **was installed**, while a generated Codex agent TOML file retained a link relative to its old location. `check` reads Markdown in Skill folders; it does not inspect generated agent TOML or prove how an agent resolves it. Existing structure and security checks are useful before publishing. This tool adds one narrow check: compare the skill folder you intend to ship with the copy users will actually install. ## Quick start Try the [folder comparison](https://lydiatools.github.io/skill-bundle-check/web/diff.html) or [table-escape review](https://lydiatools.github.io/skill-bundle-check/web/) in your browser without installing Node. Use Node.js 20 or later. Cloning the repository requires network access; once the files are on your machine, the checks need no dependencies, account, or network access. ```bash git clone https://github.com/LydiaTools/skill-bundle-check.git cd skill-bundle-check node src/cli.js check ./examples/source ./examples/installed ``` To see the multi-agent update comparison, run `node examples/update-demo.js`. To try a changed installed copy, run `node examples/diff-demo.js`. It uses fictional files in a temporary directory. The included broken installation shows what a missing reference looks like. Run this command; exit code `1` is expected: ```bash node src/cli.js check ./examples/source ./examples/installed-missing ``` ```text REFERENCE_MISSING_FROM_INSTALL installed/SKILL.md:8 Referenced file is missing: references/setup.md FAIL 2 local references checked source: 2 Markdown files · installed: 1 Markdown files ``` Run it against a real installation or build output: ```bash node src/cli.js check ./skills/my-skill ~/.agents/skills/my-skill ``` The first path is the source skill folder containing `SKILL.md`. The second is the exact installed or packaged folder to verify. The command only reads files; it does not run install scripts or skill code. The source or installed folder may be a symbolic link to a separate directory. The checker resolves the folder before comparing; references inside the bundle are still checked for escaping its resolved root. In an isolated test, `skills@1.7.4` created a Claude Code symlink when installing the same synthetic Skill for Claude Code and Cursor; v0.3.0 rejected that installed path, while v0.4.0 checks it. This does not establish that every installer or platform uses symlinks. Check whether an agent has a Skill at its documented global path: ```bash node src/cli.js check-agent --agent claude-code --skill my-skill --scope global node src/cli.js check-agent --agent codex-cli --skill my-skill --scope global node src/cli.js check-agent --agent antigravity-cli --skill my-skill --scope global node src/cli.js check-agent --agent antigravity-ide --skill my-skill --scope global ``` To see the documented global location for every built-in profile at once: ```bash node src/cli.js check-agent --agent all --skill my-skill --scope global ``` Use `--scope project` and `--cwd /path/to/project` for a project directory. The report checks file placement only; it does not query a running agent or prove that a Skill was loaded. Missing paths are normal findings in this locate report, so the command exits `0` when the scan completes and `2` if a path cannot be inspected. JSON includes absolute paths; review them before sharing because they can contain local usernames or directory names. Two profiles may refer to the same physical root. For a repository-local Skill, use `--scope project`: ```bash node src/cli.js check-agent --agent claude-code --skill my-skill --scope project node src/cli.js check-agent --agent codex-cli --skill my-skill --scope project ``` If the Claude Code project path is missing but the same Skill exists under the current project's `.agents/skills/`, v0.14.3 reports that other location and still exits `1` for the missing expected path. This helps investigate the cross-agent directory mismatch discussed in [Claude Code #31005](https://github.com/anthropics/claude-code/issues/31005); it does not install, link or verify runtime discovery. Run from the project directory or pass `--cwd /path/to/project`. The older v0.14.2 download does not include this project-root hint. For another agent, pass its documented Skills root directly: ```bash node src/cli.js check-agent --root ./custom-agent/skills --skill my-skill --scope global ``` Built-in profiles cover `claude-code`, `codex-cli`, `antigravity-cli`, `antigravity-ide`, and `antigravity-app`. Profile paths link to the platform documentation used for the mapping: [Claude Code Skills](https://code.claude.com/docs/en/skills), [Codex Skills](https://developers.openai.com/codex/skills/), and [Antigravity Skills](https://www.antigravity.google/docs/skills). Project scope checks the project directory represented by the current working directory. A single-profile check returns exit code 1 when its expected path is missing. If the Skill is found in `~/.agents/skills` but not in the selected global root, the report shows both paths. A documented legacy Antigravity IDE path is also recognized. This checks file placement; it does not confirm runtime discovery or execution. From v0.14.4, when the expected `SKILL.md` exists through symbolic links, `check-agent` lists the link paths on the selected route. This helps diagnose discovery problems without asserting whether the agent follows them. [Claude Code issue #14836](https://github.com/anthropics/claude-code/issues/14836) contains version-specific reports. If an expected path contains a broken symbolic link, `check-agent` also shows the broken link. A [Codex report](https://github.com/openai/codex/issues/11314) was traced to a relative link pointing at the wrong location; this check diagnoses file paths, not agent loading. ## Scan installed Skills for broken paths Use `doctor` when you want to inspect several Skills at once instead of naming one Skill at a time: ```bash node src/cli.js doctor \ claude="$HOME/.claude/skills" \ codex="$HOME/.agents/skills" \ --format text ``` The scan checks immediate, non-hidden directories and directory symlinks in each selected root. It reports whether each entry has a readable `SKILL.md`, including broken links; it does not follow nested Skills or inspect their referenced files. JSON output includes the selected absolute roots, which may reveal local usernames or directory names, so review it before sharing. More than 2,000 entries in a root is marked as truncated and exits with code 2. Exit code 0 means all scanned entries were found, 1 means a selected root or entry is missing or broken, and 2 means a root could not be inspected, the scan was truncated, or input was invalid. This is a filesystem snapshot, not an agent-runtime check or repair command. From v0.4.0, Codex global checks look in both `~/.agents/skills` and `$CODEX_HOME/skills` (default `~/.codex/skills`) and report every matching root. Set `CODEX_HOME` for the process, or use `--codex-home /path/to/codex-home`; when using `--home` for a fixture, the default Codex home is `.codex` under that home. An isolated native Codex app-server `skills/list` test found separate synthetic Skills in both user roots. File presence alone still does not prove that your running agent loaded a particular Skill; versions and configuration may differ. Reproduce an install-path mismatch with the included synthetic fixture: ```bash node src/cli.js check-agent --agent antigravity-cli --skill probe-skill --scope global --home ./examples/agent-paths ``` The command intentionally exits with code 1 and reports that `probe-skill` exists under the shared `.agents/skills` root, not Antigravity CLI's documented global root. No agent is launched. ## Check a destination before installing Two different Skills can have the same name. The UI-design Skill [unslop](https://github.com/heydamir/unslop/issues/3) and a writing Skill share one; a contributor's [closed, unmerged install PR](https://github.com/heydamir/unslop/pull/5) describes how a recursive copy can overwrite files in an existing destination. In an isolated macOS test, copying two fictional same-name Skill folders replaced the first `SKILL.md`. Before copying, inspect the **exact destination path** your installer will use: ```sh node src/cli.js check-target "$HOME/.claude/skills/unslop" ``` `PRESENT` means that path currently exists, even if it is an empty directory or a dangling symbolic link: inspect it before proceeding. `MISSING` means the first missing component was absent at the moment of inspection; `UNAVAILABLE` means the tool could not check it, for example because a parent is a broken link or not a directory. Exit codes are `1`, `0`, and `2` respectively. Add `--format json` for structured output. This is a read-only snapshot, not a reservation, an installer simulation, a backup, or a guarantee that a later copy is safe. Confirm the actual destination, inspect existing files, and keep a backup before replacing anything. Paths in the output can contain personal information. Behavior differs by installer, shell, filesystem and timing. ## Review a single-Skill ZIP If an uploader rejects a ZIP, [choose it in the browser](https://lydiatools.github.io/skill-bundle-check/web/zip.html). The file stays in the tab; only ZIP directory metadata is read. The browser version supports UTF-8 and ASCII entry names; legacy non-ASCII names and Unicode Path extra fields are not supported. If the only `SKILL.md` is loose at the ZIP root, the checker points Claude web and desktop users to the platform's top-level folder instructions. This hint does not check the rest of the layout or verify an upload. It is included in v0.14.2; the fixed v0.14.1 download predates it. To use this page from the downloaded ZIP, extract it, open a terminal in the extracted folder, and run `python3 -m http.server 8000 --bind 127.0.0.1` (on Windows, use `py -3` in place of `python3`). Open `http://127.0.0.1:8000/web/zip.html` in your browser. Stop the server with Ctrl+C. The page reads selected ZIPs in your browser and does not send them to the server. ![Actual browser ZIP review showing two entry files and a symlink in the labelled fictional example](docs/assets/zip-review-en.png) *Actual browser view using the included fictional example. No real Skill is loaded in this screenshot.* Or use Python 3.9+: ```sh python3 scripts/check_skill_zip.py /path/to/your-skill.zip ``` The read-only check reports the number and paths of exact-case `SKILL.md` entries and flags Unix-mode symlinks, duplicate archive paths, encrypted entries, unsafe paths and case variants. It does not extract or execute files. Exit `0` means these checks found no concerns; `1` means review the findings; `2` means the archive could not be inspected. Add `--json` for a machine-readable report. For a real historical example, [Humanizer #224](https://github.com/blader/humanizer/issues/224) reported an uploader rejecting a symlink. We checked the GitHub source archive at commit [`43c9767`](https://github.com/blader/humanizer/tree/43c97670b563cfa75e4f16ef00c32e933104d10a): this tool reported one symlink and two `SKILL.md` entries. The upstream [fix](https://github.com/blader/humanizer/pull/226) published a separate single-file package; its v2.11.1 release ZIP produced no findings in this check. This is a historical example, not a statement about current releases. We did not upload either ZIP to Claude. This is for a **single-Skill** upload, not a multi-skill plugin validator. Platform rules differ; a clean result does not prove an upload will succeed or an agent will load the Skill. The tool reads directory metadata only: it does not validate YAML, file contents, compression integrity, platform policies or security. Archives over 64 MiB, ZIP64, multi-disk ZIPs, more than 5,000 entries, directories over 4 MiB, trailing data and comments containing an end-record signature are unsupported. ## Try a fictional update See the before/after check without installing an Agent Skill: ```bash node examples/update-demo.js ``` The demo creates two fictional Skill folders in a new temporary directory, removes one to simulate an update, and runs the real CLI. It prints `claude: found -> found` and `codex: found -> missing`; the comparison returns exit 1, while the successfully completed demo itself returns exit 0. The demo then removes its temporary directory. It does not touch your installed Skills. ## Review a command hidden inside a table [Try table escape review online](https://lydiatools.github.io/skill-bundle-check/web/) · [中文](https://lydiatools.github.io/skill-bundle-check/web/?lang=zh) ![Actual online table review with fictional Markdown and two review hints](docs/assets/pipe-review-web.png) The page checks pasted or selected Markdown in your browser, without executing it. The web page only covers this table-escape review; installation and bundle checks remain in the CLI. A table can show a pipe while the raw Skill file contains a backslash before it. Is the backslash part of the intended command? That depends on the shell and regex syntax. [GitHub documents table escaping](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables); [leanrea #1](https://github.com/aicodeking/leanrea/issues/1) reports one real case where copied commands behaved differently. ```bash node src/cli.js review-pipes examples/table-pipes.md node src/cli.js review-pipes /path/to/SKILL.md --format json ``` The fictional example gives two **review hints**, including a deliberately literal extended-regex pipe. Results name the file and 1-based line and UTF-16 column of the backslash. Hints exit 0; unreadable files or invalid input exit 2. This approximate scan covers inline code on ordinary single-line pipe-table rows; it is not a full Markdown or shell parser and can miss or over-report cases. Output stops at 1,000 hints and explicitly reports truncation when more exist. An escape can be correct (for example GNU basic-regex alternation), and a clean scan does not prove commands work. It never runs, interprets or changes a command. Check each result in context; a fenced code block outside a table can make commands easier to inspect in raw and rendered views. ## Review script paths in shell examples An audit can look in the wrong directory and report a missing script that is actually present. A [HashiCorp issue](https://github.com/hashicorp/agent-skills/issues/56) was later identified in its comments as such a false positive. In the repository snapshot we checked, the referenced script existed relative to the skill folder. The current `main` may differ. The regular `check` deliberately skips fenced code. Use this separate, non-blocking review to compare selected `./scripts/` command paths in the **source root SKILL.md** against both folder roots: ```bash node src/cli.js review-shell ./examples/shell-source ./examples/shell-installed node src/cli.js review-shell ./skills/my-skill ~/.agents/skills/my-skill --format json ``` The included fictional example reports `source-root=file` and `installed-root=missing`. These are root-relative file observations, **not a verdict that the command is broken**: the instructions may intend a different working directory. The scan recognizes direct commands and `sh`, `bash`, `zsh`, `python`, `python3` or `node` invocations on simple `./scripts/` paths in labeled shell fences only. It does not parse shell, inspect other Markdown files, run the command, establish file integrity, or prove agent execution. It can miss or over-report candidates; at most 1,000 hints are returned, with truncation flagged. Hints exit 0; invalid or unreadable input exits 2. Verify the intended working directory and command before drawing a conclusion. ## Compare installations before and after an update An update can leave a Skill present for one agent and missing for another. The open [Spec Kit report #5002](https://github.com/github/spec-kit/issues/5002) describes this in one Claude/Codex configuration; [a proposed fix](https://github.com/github/spec-kit/pull/5005) is under review. The check below observes files, not whether an agent actually loads them. From this repository, choose the same skill and explicitly named roots each time: ```bash node src/cli.js snapshot speckit-git-feature \ claude=/path/to/project/.claude/skills codex=/path/to/project/.agents/skills > before.json # Perform your normal update in the project, then run the same check: node src/cli.js snapshot speckit-git-feature \ claude=/path/to/project/.claude/skills codex=/path/to/project/.agents/skills > after.json node src/cli.js compare before.json after.json ``` JSON reports `found`, `missing`, `broken-link`, `not-file`, or `unavailable`. Snapshot exits 1 when a target is missing, broken or not a file; compare exits 1 when any target is missing, broken or not a file in the after snapshot. An unavailable target in either comparison snapshot, invalid input, or mismatched target sets exits 2. A snapshot containing any missing target still writes JSON and exits 1, so do not chain it with `&&` if you need the comparison. In one isolated macOS reproduction, Spec Kit v0.12.4 installed `speckit-git-feature` for Claude and Codex. After upgrading both integrations with v1.2.1 and updating the git extension from 1.0.0 to 1.0.1, the comparison showed Claude `found → found` and Codex `found → missing` (exit 1). This is one version-specific observation, not a claim about current versions or agent runtime. Root paths in the JSON are absolute and may contain personal information; review them before sharing. Two names may point to the same physical directory; they are not proof of independent copies. The tool reads presence at the time of each check and does not back up, restore, prevent deletion, compare contents or establish agent discovery. ## Compare two copies after an update [Compare browser-provided folder files](https://lydiatools.github.io/skill-bundle-check/web/diff.html) without installing Node. Files stay in the tab. Folder selection support depends on the browser; hidden files, empty folders and symbolic links may be omitted, so a match does not verify full filesystem contents or Agent loading. The page cannot establish whether two selections refer to distinct filesystem directories. ![Browser comparison of two explicitly fictional Skill folders, showing one changed file](docs/assets/skill-diff-web.png) *The built-in example uses fictional files.* You update a skill in its source folder. Is the copy your agent can access still the same? Compare the two folders you select: ```bash node src/cli.js diff ./skills/my-skill ~/.agents/skills/my-skill ``` For example, in an isolated test with `skills@1.7.4`, a local skill installed with `--copy` stayed at v1 after its source changed to v2. The installer reported that local sources could not be checked automatically and suggested re-adding it. `diff` identified the changed `SKILL.md`. This is one tested setup; behavior depends on installer version and mode. [Original local-update report](https://github.com/vercel-labs/skills/issues/1440). Added your own notes inside an installed Skill? [See the backup-and-compare walkthrough](docs/local-files-after-update.md) based on a reported `gh skill update` case and an isolated test. This read-only command lists differing relative paths and whether each was added, removed or changed. Add `--format json` to include SHA-256 values for CI. Exit 0 means the compared file bytes matched; 1 means differences; 2 means the check could not complete. It does not output file contents, select the authoritative copy, determine what the agent loaded, or update either folder. This is a snapshot: do not edit the trees during comparison. Empty directory-only changes are not compared. Both roots must be separate, non-overlapping existing directories with a regular `SKILL.md` at each root. Inner symbolic links and special files are refused; a root itself may resolve through a symlink. The scan stops rather than report a partial match above 2,000 entries, 8 MiB per file or 64 MiB total per directory. This is not an atomic security boundary against concurrent hostile filesystem changes. Check actual installed paths and output before sharing. <a id="plugin-tree"></a> ## When a Skill is part of a plugin The Skill file can match while the plugin around it is missing. In [Vercel Skills #2609](https://github.com/vercel-labs/skills/issues/2609), a user reports an installation that copies a nested Skill without the enclosing Claude Code plugin metadata and hooks. In our isolated macOS test with `skills@1.7.4` and a fictional plugin, comparing just the nested Skill returned a match; comparing the selected plugin source with the installed Skill revealed the missing relative paths. Try a fictional version of that comparison: ```bash node src/cli.js diff-tree ./examples/plugin-source ./examples/plugin-installed ``` The example reports `.claude-plugin/plugin.json` and `hooks/hooks.json` as source-only, along with paths that differ because the Skill was moved; exit 1 is expected. For your own package, select the actual source plugin root and the actual installed folder you want to compare. Both directories must exist; the source must contain at least one regular file. Relative paths must have the same layout for a byte-for-byte match; an intentional reorganization also appears as differences. `diff-tree` uses the same read limits and exit codes as `diff`, but does not require `SKILL.md` at either root. It compares files, not empty directories, and does not prove plugin loading, hook execution or that a chosen path is correct. ## GitHub Actions Run your normal packaging/install step first, then check its output: ```yaml steps: - uses: actions/checkout@v4 - name: Build skill bundle run: ./scripts/build-skill.sh - uses: LydiaTools/skill-bundle-check@v0.9.0 with: source: ./skills/my-skill installed: ./dist/my-skill ``` Findings become inline GitHub annotations. For a local JSON report: ```bash node src/cli.js check ./skills/my-skill ./dist/my-skill --format json ``` ## What it checks - `SKILL.md` exists in both folders. - Local links in Markdown and HTML references point to files or directories that exist in the source. - Referenced files remain present at the same relative paths in the installed bundle. - Relative links in the installed copy resolve inside that bundle. - Absolute paths, missing files, broken symlinks, and links that escape the bundle root are reported with file and line. It reads Markdown links, reference-style link definitions, HTML `href`/`src`, and conventional `assets/`, `references/`, or `scripts/` paths written in inline code. Markdown links and explicit `./` or `../` paths are checked relative to their document. For an unqualified inline path in a nested document, it also considers the Skill root: if both locations exist, it flags the ambiguity for review. If only one exists it checks that location, but cannot establish the author's intended working directory. It does not parse every Markdown extension or execute examples. `check-agent` checks for the selected Skill's `SKILL.md` at the chosen documented root. Built-in paths link to the platform documentation used for that mapping; custom roots are checked exactly as supplied. ## Examples The fixture models a package with a supporting file preserved: ```text examples/ ├── source/ │ ├── SKILL.md │ └── references/setup.md ├── installed/ │ ├── SKILL.md │ └── references/setup.md └── installed-missing/ └── SKILL.md ``` If `references/setup.md` is omitted from `installed/`, the check fails and reports the source line that still points to it. ## Development ```bash npm test ``` ## License MIT. Source code is original to this repository; the cited issues are examples of reported problems, not endorsements.

Carregando o README do repositório…

Skills neste repositório

classificação pendente

skill

ocupação

descrição

atualizado

example-skill

sem classificação

Fictional demonstration skill.

Idioma do texto original: Indeterminado

2026-10-31

probe-skill

sem classificação

Synthetic example for checking whether an agent path contains a skill.

Idioma do texto original: inglês

2026-10-27

example-skill

sem classificação

A small fixture showing how to check an installed skill bundle.

Idioma do texto original: inglês

2026-10-26

example-skill

sem classificação

A small fixture showing how to check an installed skill bundle.

Idioma do texto original: inglês

2026-10-26

Mostrando 4 de 4 skills coletadas.