Read the house build's site camera and review source-cited construction payment proposals through protected owner callbacks and a host-owned append journal.
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
Overlay for the house build: the site camera, and the construction payments sheet tracked in nanoclaw#1039.
tessl install jbaruch/nanoclaw-constructionInstallation loads the skills and their rules.
construction-site answers «чо там как на стройке» from the camera frames on main's
read-only construction-site mount, and saves a digest each evening at 18:30 site time
for the morning brief. It reads frames only.
construction-costs turns a forwarded invoice or payment notice into a five-cell row
(date, purpose, payee, amount, method), shows it on a Да/Нет card and, after «Записать»,
appends it to the «Construction costs» sheet with scripts/costs.py, which refuses an
identical row and reads the written row back. It needs a Google Sheets connection on
main's OneCLI tier and /workspace/group/construction-costs.json with the sheet_id.
It never creates bank payments.
Run checks with the pinned requirements-dev.txt tools and unittest.
| Rule | Purpose |
|---|---|
| nanoclaw-skill-root | Resolve fixed installed skill paths. |
| Skill | Purpose |
|---|---|
| construction-costs | Turn a payment into a row, ask on a Да/Нет card, append it after «Записать». |
| construction-site | Answer site questions from the camera frames and save the daily digest. |
The .github/fleet-review-enabled marker enrolls independent policy and code
quality review. .github/workflows/publish.yml publishes each merge to main
through the shared coding-policy publish workflow, like the other NanoClaw
plugins, and stamps CHANGELOG.md.
Publication does not establish native runtime acceptance. This package contains no financial data or credentials.