site-inspection-storage

Persists site inspection reports to gbrain with standardized frontmatter and path conventions.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/tapway/shogun-os --skill site-inspection-storage-tapway
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: site-inspection-storage
Source: https://github.com/tapway/shogun-os/tree/main/industries/plantation/skills/site-inspection-storage
Command: npx skills add https://github.com/tapway/shogun-os --skill site-inspection-storage-tapway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Site inspection results need to be stored consistently so they can be retrieved, filtered, and traced back to their source later. This Skill writes a completed inspection assessment to gbrain at the correct path with proper frontmatter, eliminating ad-hoc or misplaced storage. ## Core Features & Use Cases - Standardized Storage Path: Writes reports to references/inspections/<date>-<location>.md, with a fallback for unspecified locations. - Structured Page Template: Generates a gbrain page with frontmatter (source, inspected date, location, overall_rating) and sections for furniture inventory, cleanliness, site condition, safety, and priority actions. - Traceability: Records the original source (e.g., a Telegram file ID) so every report links back to the original photo or video. - Use Case: After a staff-quarters inspection is assessed from a Telegram photo, save the structured assessment to gbrain so facilities staff can later filter inspections by rating or location. ## Quick Start Save this completed site inspection assessment to gbrain with its source reference and location.

Frequently Asked Questions about site-inspection-storage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save a site inspection report to gbrain?▼

Pass the completed assessment object, source reference, and location to this Skill, which calls the gbrain MCP put_page tool. The report is written to references/inspections/<date>-<location>.md with standardized frontmatter.

What input does site inspection storage require?▼

It requires a JSON object containing the assessment from site-condition-assessment, a source identifier such as a Telegram file ID, and the location. It does not accept raw photos or videos directly.

Does this Skill assess inspection photos or videos?▼

No, assessment is explicitly out of scope and handled by the separate site-condition-assessment Skill. This Skill only stores an already-produced structured assessment to gbrain.

What happens if the inspection location is not identifiable?▼

The report is stored using a fallback filename such as 2026-08-15-unspecified.md under the references/inspections/ directory, so the record is still persisted without a location slug.

Why is the overall_rating field required in the frontmatter?▼

The overall_rating frontmatter field enables filtering inspections by rating later in gbrain. Omitting it means reports cannot be queried or sorted by condition, which the Skill lists as a key pitfall.