zqtest
Analysis
This looks like a local ontology memory tool, but it needs review because its documentation promises enforced validation and secret-protection that the visible write helper does not appear to enforce.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
def create_entity(...): entity = {"id": entity_id, "type": type_name, "properties": properties, ...}; record = {"op": "create", "entity": entity, ...}; append_op(graph_path, record)The visible create path accepts arbitrary properties and appends them to storage. In context, SKILL.md claims 'Every mutation is validated against type constraints before committing' and defines forbidden credential properties, so users or agents may overtrust validation that is not evident in the write helper.
{"ownerId": "kn72dv4fm7ss7swbq47nnpad9x7zy2jh", "slug": "ontology", "version": "1.0.4"}The package-internal metadata differs from the registry metadata shown for this evaluation, which lists owner kn75a5r3vfnrs608hxn6hqbkwn834s6p, slug zqtest, and version 1.0.0. This is a provenance inconsistency, although the included files otherwise align with the ontology purpose.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Default: `memory/ontology/graph.jsonl` ... `Skill needs shared state | Read/write ontology objects` ... `Person: { name, email?, phone?, notes? }` ... `Message: { content, sender, recipients[], thread? }`The skill intentionally creates a persistent shared memory graph that can contain personal and communication data. This is central to the stated purpose, but it means stored entries may be reused by future tasks or other skills.
