Real Skill packageSource verifiedClawHub registry

rez-package-pitfalls

The package.py execution model and the errors it produces — why a top-level `from x import SomeClass` makes the installed package.py unparseable, why module-scope values are frozen on the build machine, why `env`/`this`/`root` look undefined to linters, and why a failed rez-build can leave a broken install behind. Use when a package resolves or builds with a confusing error, when reviewing a package.py for module-scope mistakes, or before releasing one. Covers Rez 3.4.0.

Identity and source

Publisher attributionHalregistry owner unverified by skillvetai
Functional categoryAwaiting category reviewreview pending · 0% rule confidence
Package forminstruction bundle2 recorded files
Canonical sourceClawHub registryclawhub:loonghao:rez-package-pitfalls
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 10/2/2026.claude/skills/rez-package-pitfalls

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 10/2/2026.agents/skills/rez-package-pitfalls

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 10/2/2026skills/rez-package-pitfalls

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

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 @loonghao/rez-package-pitfalls
clawhub inspect @loonghao/rez-package-pitfalls --version 1.0.2

Security evidence

SkillVetAI static result: no findings detected

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
2 / 2 inspected as text
Checked
10/2/2026, 5:33:28 AM
Scanner
0.1.3
Policy
1.0.3
3 inferred permission indicators
  • network access — automatically inferred
  • filesystem write — automatically inferred
  • credential access — automatically inferred
1 dependency and API indicators
  • api: clawhub.ai
External clawhub result: clean

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.

Evidence checked
10/1/2026, 9:58:15 PM
Release binding
Matches this record
  • vt: clean
  • skillspector: suspicious
  • llm: clean

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:b679d56d90bb7d3c5cd61320515de1846f8d12cc332d0618c12d5268e4572db5
Show up to 2 recorded paths
  • skill-card.md
  • SKILL.md

Source changelog

rez-package-pitfalls 1.0.2 - Clarified that a failed rez-build can, but does not always, leave a broken install behind (Pitfall 4). - Updated explanations to reflect that some failures (e.g., environment-resolution errors) do not actually install a broken package. - Improved instructions for checking and removing partial or broken installs after failed builds. - Removed redundant documentation file (skill-card.md).

Release security diff

mediumCompared fixed releases 1.0.0 and 1.0.2; 0 finding and 1 permission indicators were added.

Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.

Permission escalation detected
Change reasons and limitations
  • permission surface changed
  • dependency surface changed
  • file surface changed
  • content hash changed

Observed release history

These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.

1.0.010/1/2026sha256:271cff163440e76baf56ca8779971fb94742ea856f5e0b6738a04174a1a96eb2