Skip to content
Back to skills

Inventory Reference Items

ASecurity

Build a structured inventory of externally established reference items under a parent-specified schema, preserving applicability/status, key attributes, limitations, and provenance. Typical schemas include benchmark or known-solution/method family.

  • 499 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
researchnode

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill inventory-reference-items --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Inventory Reference Items?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Inventory Reference Items
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-inventory-reference-items/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-inventory-reference-items)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: inventory-reference-items
description: "Build a structured inventory of externally established reference items under a parent-specified schema, preserving applicability/status, key attributes, limitations, and provenance. Typical schemas include benchmark or known-solution/method family."
---

# inventory-reference-items

## Purpose

Build a structured inventory of externally established reference items under a caller-specified schema.

## Input contract

```yaml
required: [reference_items, item_schema, applicability_rules]
optional: [known_solutions, benchmarks, source_scope, status_vocabulary]
constraints: [preserve applicability, status, limitations, key attributes, and provenance for every item]
```

## Procedure

1. Define the eligible reference universe and normalize item identifiers.
2. Extract schema fields, applicability, status, limitations, and provenance.
3. Deduplicate items without merging distinct benchmarks or methods.
4. Return the inventory with exclusions and unresolved provenance.

If reference items expose the metrics used for comparison, consider `decompose-evaluation-metric` as the next tactic.

## Output contract

```yaml
produces: [reference_inventory, applicability_map, limitation_register, provenance_index]
delta_fields: [findings, evidence_updates, uncertainties]
```

## Quality gates

- Every item has a stable identifier, source reference, applicability status, and limitation note.
- Benchmark and known-solution inventories remain schema-distinct when their fields differ.
- Missing fields are explicit; no benchmark or solution is inferred from a similar name.

## Parameterization

The caller must provide item type, schema, eligible source scope, inclusion/status rules, canonical identifier policy, and required provenance fields.

## Failure and counterexamples

Reject inventory entries with no provenance, mixed item types under one schema, or deduplication that removes a distinct reference item.

## Provenance map

- concept: knowledge-acquisition/benchmark-inventory
- intermediate: Pass4/inventory-benchmarks
- concept: creative-ideation/benchmark-inventory
- intermediate: Pass4/inventory-known-solutions

## Preserved source criteria ledger

No resolved v3 source node was present for these four entries; they remain explicitly marked concept/intermediate and are not replaced by a similarly named inventory.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…