Reading the USER's HASH graph. Use before asking the USER for a fact their organisation may already record (a supplier, product, site, machine, role or figure), and before any HASH read.
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
The USER works inside HASH, and their organisation may already record much of what you would otherwise ask. Don't ask for what the graph holds: read it, bring what you found to the USER, and ask only for what it lacks or to confirm what it says.
linkData).editionId names the one you read. A later read may return a later one.entityId carries a third part (webId~entityUuid~draftId), and reading by that id reads the draft. It also retains reached draft links whose left or right endpoint is an explicitly named draft, but does not include other draft endpoint records or recursively include further draft links. Link endpoint ids remain intact even when the endpoint record is excluded. Use includeDrafts: true to include all reached drafts.Records say what was entered, not what happens. What happened last Tuesday, or how practice bends a rule, is still the USER's to tell.
hash_query_webs, to learn the USER's web and their organisations'.hash_query_entities by webIds from those webs, and by type title if you already know it, with traversalDepth: 0, to see what records each web holds. A title in entityTypes matches every type with that title, in any web and at any version; a versioned entityTypeId matches that version only.hash_query_entity_types with the entityTypeIds those entities carry, to learn the properties and links those types allow, set or not. Without filters it lists the types the USER can see only up to the graph's limit, which is large: filter by entityTypeIds.entityId rather than widening the filter. Use a traversalDepth above 0 only when links matter, such as which supplier provides a part, and go no deeper than they need. It is at most 3; each link is followed in either direction, so mixed chains (A → B ← C) are included, and reading a link entity includes its endpoints.Reads come back as compact text. An entity read lists each property by a short name with its title and description once at the top, where any unit is stated. The short name comes from the property type's base URL (…/property-type/planned-delivery-time/ shows as planned_delivery_time) and holds only within that read: when two properties anywhere in a read, nested values included, would share one, both show by their full base URL instead, so the same property can carry another name in another read. An entity type read names its properties the same way, within its own read. Name properties by title to the USER, and match them across reads by title, or by base URL where one is shown, not by short name. The read also lists each entity type title with its entityTypeId; then each entity, headed by its types' titles, with its entityId, editionId and one line per property. When two types in a read share a title, such as two versions of Supplier, the heading gives each its entityTypeId too. A large value, such as a process definition, shows as <object, 8.5 KB: 3 places, …>. When you need it, read that entity again by entityIds with its id in fullValuesFor.
evidenced origin, with the entity's title, entityId and editionId in the claim text: the edition is the version the value came from, and a later edition may hold another. Commit it in the exchange where you found it, before any net change that relies on it. Its status is tentative until the USER confirms the value itself holds for this operation, and conflicted when their account disagrees. Being asked to use a record is not confirmation of its value.error and note is a failed read, not an empty one. Narrow the read or retry it; if it still fails, tell the USER the lookup failed and ask instead.editionId, since the record may since have changed.hashintel/hash
55a48dd
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.