@specset/cli 0.4.0 → 0.5.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/main.js +1595 -205
- package/package.json +1 -1
- package/skills/specset-tools/SKILL.md +37 -0
package/package.json
CHANGED
|
@@ -56,6 +56,43 @@ Tool results embed identifiers shaped like `sb://spec/<uuid>` or `sb://drawing/<
|
|
|
56
56
|
|
|
57
57
|
Most tools are project-scoped. Either pass `--project` (a UUID or `sb://project/...`), or include `projectId` in the tool input. Use `listProjects` to discover project IDs. With `--project` set, per-call `projectId` becomes optional.
|
|
58
58
|
|
|
59
|
+
## Downloading source files (drawings, documents, specs, submittals, RFIs)
|
|
60
|
+
|
|
61
|
+
The retrieval tools return **extracted text**, which is authoritative for schedules, notes, and spec paragraphs — but cannot answer spatial/visual questions (routing, clearances, what a plan view actually shows) and never carries the original file. Every entity has a download command, and **each accepts its `sb://` citation URL verbatim** (as returned by issues, search, and tool results — any `#page=`/`#nodeId=` fragment is ignored) or a bare UUID:
|
|
62
|
+
|
|
63
|
+
```bash
|
|
64
|
+
# Drawing sheets — image (rendered PNG, default), pdf (single-sheet), file (whole set).
|
|
65
|
+
# Also accepts a sheet number with --project. Read the PNG with vision to inspect geometry.
|
|
66
|
+
specset drawings download 'sb://drawing/<uuid>#nodeId=d1' --out /tmp/sheets/
|
|
67
|
+
specset drawings download E308 --project <projectId> --format pdf
|
|
68
|
+
|
|
69
|
+
# Project documents — also covers RFI attachments and closeout documents,
|
|
70
|
+
# which all reference a document:
|
|
71
|
+
specset docs download 'sb://doc/<uuid>'
|
|
72
|
+
|
|
73
|
+
# Spec sections — per-section PDF slice (default) or the whole source spec file.
|
|
74
|
+
# Also accepts a section number with --project:
|
|
75
|
+
specset specs download '23 31 19' --project <projectId>
|
|
76
|
+
specset specs download 'sb://spec/<uuid>' --asset book
|
|
77
|
+
|
|
78
|
+
# Submittals — compiled package (default when present), cover sheet, or attachments.
|
|
79
|
+
# --list shows the asset inventory first:
|
|
80
|
+
specset submittals download 'sb://sub/<uuid>' --list
|
|
81
|
+
specset submittals download 'sb://sub/<uuid>' --asset attachment --index 2
|
|
82
|
+
specset submittals download 'sb://sub/<uuid>' --asset attachment --all --out ./sub-42/
|
|
83
|
+
|
|
84
|
+
# RFIs — question + response attachments:
|
|
85
|
+
specset rfis download 'sb://rfi/<uuid>' --list
|
|
86
|
+
specset rfis download 'sb://rfi/<uuid>' --all --out ./rfi-7/
|
|
87
|
+
|
|
88
|
+
# Raw file resources — the escape hatch when you already hold an sb://file id:
|
|
89
|
+
specset files download 'sb://file/<uuid>'
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
All commands support `--json` (structured `{files: [{path, bytes, ...}]}` output) and `--out` (file path, or directory for multi-file downloads). A citation passed to the wrong command errors with the right one to use.
|
|
93
|
+
|
|
94
|
+
Typical loop for drawings: search or `getDrawingSheetContent` to find the sheet → hit a visual question the text can't settle → `drawings download` → **read the PNG with your vision/file-reading tool**.
|
|
95
|
+
|
|
59
96
|
## MCP server (Claude Code, Codex, other MCP clients)
|
|
60
97
|
|
|
61
98
|
`specset mcp` runs a stdio MCP server that exposes these tools natively, reusing your CLI login, org, and host config. Register it once and the client can call the tools directly:
|