House Inventory
Manage home inventory and storage tracking with intelligent image indexing.
Install
$ agentstack add skill-kongaharsha-hermes-stack-house-inventory ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-kongaharsha-hermes-stack-house-inventory) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
House Inventory
Overview
House Inventory is a disciplined system for cataloging physical assets, tracking container contents (boxes, bags, suitcases), and maintaining a verifiable index of reference imagery. Designed for precision, speed, and consistency.
Prerequisites
- GBrain Setup: This skill requires an initialized
gbrainenvironment. If you do not have one, set it up first:
gbrain init or see GBrain Repository.
- Inventory File: A valid markdown inventory file at the configured
storage_path.
Workflow
- Cataloging: Extract objects/item descriptions from image uploads or manual text input.
- Container Indexing: Identify the source/target container (e.g., Box #1).
- Validation: Review extracted lists with the user to ensure terminology compliance before write operations.
- Persisting: Use structured
patchoperations to append or update entries while maintaining file integrity.
Format Principles
- Container-First Hierarchy: Every item must belong to a defined container.
```markdown ### Container: [Name]
- Type: [Box/Bag/Suitcase]
- Location: [Storage/Home]
- Reference Photos: [link1], [link2]
- Items: [Standardized bulleted list]
```
Standardized Terminology
- Consistency: Use precise naming conventions (e.g., "Diyas" over "Mats").
- Renaming: If descriptive terms are identified as inaccurate post-cataloging, perform an immediate refactor of the inventory entry to ensure future search accuracy.
Reliability Patterns
- Atomic Patching: All modifications to the inventory file must be done via
patchoperations to prevent data loss. - Read-Before-Write: Must read current
house-inventory.mdstate prior to execution to prevent conflicts with other agents.
Anti-Patterns
- Hardcoded Pathing: Never assume absolute local file paths outside of the
storage_pathconfiguration. - Vision Guessing: Never assume item identity from low-confidence image analysis. If ambiguous, trigger a manual verification request to the user.
- Cluttered Indexing: Do not create duplicate container entries; always verify existence before cataloging new items.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: kongaharsha
- Source: kongaharsha/hermes_stack
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.