Update to Grasp

{
  "description": "Use when the user wants to inspect, search, filter, keep/remove/exclude rows, sort, query, describe coverage, read rows, export, or recover handles for an existing Grasp table.",
  "included_files": [],
  "name": "working-with-tables",
  "skill_md_contents": "---\nname: working-with-tables\nuser-invocable: false\ndescription: Use when the user wants to inspect, search, filter, keep/remove/exclude rows, sort, query, describe coverage, read rows, export, or recover handles for an existing Grasp table.\n---\n\n# Working With Tables\n\nUse table handles deliberately. Do not guess field names. Treat `grasp_get_table` previews as samples.\n\nThis is a table-mechanics skill. If the user wants to screen, qualify, shortlist, prioritize, rank, select top-N, map a competitor landscape, or turn a long list into a decision set, use the `screening-and-shortlisting` skill; call this skill only for the underlying inspection, coverage, query, filter, sort, export, or missing-row operations.\n\n## Handles\n\n- Use UUID `table_id` values as tool handles.\n- Do not pass `table_slug` as a tool handle. Slugs are display, navigation, and SQL identifiers only.\n- If the user refers to recent work, use the `grasp_list_tables` tool to recover the UUID `table_id` and, when needed for composition, `conversation_id`.\n- If the user gives a recent async job, wait or check status to recover the UUID `table_id` and `conversation_id`.\n\n## Workflow\n\n1. Use the `grasp_get_table` tool for metadata, columns, version, row count, and links.\n2. Use the `grasp_get_table_rows` tool for focused row reads, samples, top-N pulls, filters, and sorts.\n3. Use the `grasp_describe_table` tool for missingness, top values, and distributions.\n4. Use the `grasp_query_table` tool for read-only counts, aggregations, combined criteria, and computed comparisons. Results are capped, so export when the full result set matters.\n5. Use the `grasp_export_table` tool when the user needs the full table or local analysis beyond query caps.\n\nUse rows, describe, query, or export before making full-table, top-N, or coverage claims. When summarizing table/query results, state row counts and whether the result is a preview, sample, capped query, filtered row set, or full export.\n\n## Filtering And Sorting\n\n- Call the `grasp_get_table` tool before using a field name.\n- Use the `grasp_describe_table` or `grasp_query_table` tool to check missingness, distributions, and categorical values before filtering.\n- Do not filter on a field just because it exists in another table.\n- Avoid keyword filters for semantic fit; add a narrow research column through the `table-enrichment` skill instead.\n- Use the `grasp_get_table_rows` tool for simple filtered reads and top-N pulls.\n- Use the `grasp_query_table` tool for counts, distributions, aggregations, and combined criteria.\n- Use the `grasp_update_table` tool only when the user wants the filtered/sorted view persisted in Grasp, and include a short `version_summary`.\n- If blanks remain after filtering, state that missing values were not fully tested.\n\n## Missing Company In A Table\n\n- Use the `company-lookup` skill first to validate the expected company and canonical URL/domain.\n- Inspect whether the table scope, geography (`source_geography` from `grasp_get_table`, including whether multinationals were included), source criteria, filters, size constraints, ownership constraints, and semantic research columns should include it.\n- Check whether it is present under another name, URL, or parent before calling it absent.\n- If it is outside scope, explain the mismatch.\n- If it appears to be a false negative, present it as a corrected-table/manual-add/watch item and explain the evidence gap.\n\nUse the `grasp_read_docs` tool for SQL, filters, exports, or data-column details when uncertain.\n"
}