← PortravoCONTENT HISTORY
WHAT CHANGED
Update to Portravo
Snapshot Oct 28, 2026 · 12:54 UTC · version 1.1.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Portravo and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Turn actual Portravo takeoff notes, unresolved lines and source gaps into an estimator checklist and draft clarification questions.",
"included_files": [],
"name": "portravo-scope-questions",
"skill_md_contents": "---\nname: portravo-scope-questions\ndescription: \"Turn actual Portravo takeoff notes, unresolved lines and source gaps into an estimator checklist and draft clarification questions.\"\n---\n\n# Prepare scope questions from evidence\n\nUse https://portravo.com/mcp through normal OAuth. Resolve the actual owned project with `list_projects`, recover running work with `get_takeoff_status`, and read `get_takeoff` when results exist. Connection help: https://portravo.com/developers/mcp. A request for clarification does not authorize a new extraction or credit use.\n\nTrace each question to actual returned line notes, confidence, assembly mapping, source links or scope notes the user supplies. Preserve exact line IDs and source references. Low-confidence lines and missing mappings need review; no lines for a trade or page do not prove that scope was omitted. A page can be a title, note or detail sheet. Do not infer full sheet coverage from pages represented on quantity lines.\n\nPrepare a checklist of assumptions to confirm, unmapped lines, unresolved or unsupported scope and specific drawing questions. Distinguish the absence of evidence from a verified omission. Use the user’s relevant trades and recipient role only when that information changes the questions. A general pre-bid checklist is possible without a connection, but label it general and do not attribute it to a plan you have not read.\n\nDraft one concrete request-for-information question per material uncertainty, with actual reference, the question and what quantity or pricing decision depends on the answer. Do not accuse the designer, invent code requirements, fill missing quantities with typical scope or claim engineering/compliance conclusions. Drafts are for the user to review and send; this workflow sends nothing.\n\nReturn the owned project reviewUrl for estimator resolution. These tools do not add/fix lines or set review status. Do not rerun a takeoff merely to recover old scope notes, and do not promise whole-plan accuracy from selected lines.\n"
}SHA-256 of public snapshot: 68aa3e3b7952127579ccf7a1d333b7e81919aff35b7b6cac089e2af39a34e6cc