Skip to content

AlpacaLabsLLC/skills-for-architects / skills/site-visit-report

site-visit-report

Verified

Prepare a sourced site-visit record separating direct observations, participant reports, interpretations, limitations and proposed follow-ups.

FileKindSize
README.mdmarkdown159 B
SKILL.mdskill md4.3 KB
host-contract.jsonconfig1.5 KB
templates/site-visit-report.mdmarkdown2.6 KB

templates/site-visit-report.md

View on GitHub
# [Site visit title]

- **Visit date:** YYYY-MM-DD
- **Created:** YYYY-MM-DD
- **Updated:** Not revised | YYYY-MM-DD
- **Project / location:** [Project and site location or Unknown]
- **Visit purpose:** [Purpose and intended scope]
- **Conditions:** [Weather, lighting, occupancy, active work, or Not recorded]
- **Prepared from:** [Project-relative source links, source dates if known, or current conversation]
- **Revision note:** Not revised | [What changed and why]

## Participants

- [Name — organization or role]

## Visit Scope

- **Included:** [Locations, systems, or activities intended for observation]
- **Excluded:** [Areas or systems outside this visit]

## Direct Observations

### O1 — [Short label]

- **Location:** [Specific location or Unknown]
- **Observation:** [What was directly visible or perceived]
- **Source:** [Project-relative note, photograph, or file link]
- **Status:** Directly observed within the stated visit limitations

## Participant-Reported Information

### R1 — [Short label]

- **Statement:** [What the participant reported]
- **Attributed to:** [Participant or Unknown]
- **Source:** [Project-relative source link or current conversation]
- **Status:** Reported; not independently verified

## Interpretation

### I1 — [Short label]

- **Interpretation:** [Limited inference]
- **Basis:** [Specific O# items and sources]
- **Status:** Interpretation; requires verification and is not a compliance conclusion

## Photographs and Files

| Ref | Project-relative link | Caption / location | Supports |
|---|---|---|---|
| P1 | [Project-relative photo or file path] | [Caption] | O1 |

## Access and Visibility Limitations

- [Area not accessed, finish concealing work, lighting, equipment, testing, or documentation limitation]
- [State `Not observed`; never substitute “no issue observed”]

## Issues Requiring Review

### ISS1 — [Short label]

- **Condition:** [Observed, reported, or interpreted issue]
- **Evidence:** [O#, R#, I#, photo, or file reference]
- **Required review:** [Clarification, investigation, test, specialist, or professional review]

## Proposed Follow-Ups

### F1 — [Action]

- **Proposed owner:** [Name or Unassigned]
- **Proposed due date:** [YYYY-MM-DD or No due date]
- **Status:** Proposed from site visit; not yet recorded in `TASKS.csv`
- **Source:** [Project-relative report item or supporting source]

## Disclaimer

[For client-facing, authority-facing, or regulated-conclusion reports, replace this instruction with the canonical disclaimer block and terminal marker. A purely internal administrative draft without regulated conclusions may omit this section.]
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall