.claude/skills/update-jamdeskRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Use when user-facing code changes need documentation — after implementing APIs, CLI commands, UI components, or config options. Triggers on 'update docs', 'd...
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/update-jamdeskRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/update-jamdeskRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/update-jamdeskRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @jamdesk/update-jamdeskclawhub inspect @jamdesk/update-jamdesk --version 1.0.1This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:2d312cdfe18acce54f10b661b3eb57db0072fce2324cc7a23f61b37722ebf350skill-card.mdSKILL.md**update-jamdesk 1.0.1 – Improved accuracy and workflow for documentation updates:** - Adds explicit handling for same-repo docs: skips branch strategy questions and separate git operations when docs live in the code repo. - Enforces preflight checks for docs path, docs.json presence, CLI availability, and clean working tree before making changes. - Clarifies `--preview` flag behavior: does not create config files or ask branch-strategy questions, only describes intended changes. - Improves standards for example content: requires concrete values, fake secrets, and expected output in code snippets. - Expands guidance on troubleshooting sections, decision flow, and right-sizing doc updates (not every change needs a new page). - Multiple small clarifications and formatting improvements throughout to reinforce Jamdesk documentation standards.