name	repo-structure
description	Describes the structure of the robotic-autonomy repo — its topic folders, their purpose, and how to create and maintain work-log notes (ddmmYYYY.md format). Use this skill whenever you need to navigate the repo, add new work, or record progress for the day.

Robotic Autonomy — Repo Structure

This repo is a research initiative for building, evaluating, and deploying autonomous robot systems.

Top-level Layout

robotic-autonomy/
├── README.md                    # Project overview, objectives, current work
├── INTERESTING_WORK_NOTE.md     # Scratchpad for random research papers & links
├── agents/                      # Sub-project: agent-bench skill-as-bench framework
├── safety/                      # Sub-project: humanoid safety benchmark (MuJoCo)
└── .pi/skills/repo-structure/   # This skill

Folder Details

`agents/`

Topic: Benchmark-as-skill framework for testing robot agent loops.

Covers work on agent-bench:

New benchmark skills (e.g. maze-bench, navigation tasks)
Raycasted visual input pipeline (PNG → LLM → action)
Expanding the perceive → reason → act → repeat loop
Agent performance analysis and scoring

Work logs go here as date-named files.

`safety/`

Topic: Physics simulation (MuJoCo) stress-testing humanoid robots.

Covers work on the humanoid-safety-benchmark:

Scenario design (falls, trips, power loss, punches, kicks, body slams)
Injury metric implementation and tuning (HIC₁₅, Nij, ISO/TS 15066)
ONNX locomotion policy loading and comparison vs. passive ragdoll
Findings and regressions (e.g. Nij 0.85 in forward-fall scenarios)

Work logs go here as date-named files.

`INTERESTING_WORK_NOTE.md`

Topic: Informal scratchpad for research papers, links, and ideas thrown in on the fly.

Lives at the repo root (not a folder)
No strict format — drop a title, link, and a one-liner on why it's interesting
See the file itself for the running list

Work Log Convention

Every folder uses date-named Markdown files as work logs.

Filename format

ddmmYYYY.md

Part	Meaning	Example
`dd`	Day (zero-padded)	`08`
`mm`	Month (zero-padded)	`04`
`YYYY`	Four-digit year	`2026`

Example for 8 April 2026: 08042026.md

Suggested note template

# <Topic Folder> — 08 Apr 2026

## What I did
-

## Findings / results
-

## Blockers
-

## Next steps
-

Rules

One file per day per folder. If you work across multiple topics in a day, create a log in each relevant folder.
File lives directly inside the topic folder — no sub-directories needed for logs.
Keep logs factual and terse. Bullet points are preferred over prose.
If you reference code, link to the commit or file rather than pasting large snippets.

Adding a New Topic Folder

Create the folder at the repo root with a short, lowercase, hyphenated name.
Add a one-line README.md inside it describing the topic.
Update the layout table in this SKILL.md.
Update the top-level README.md if the topic represents a significant new workstream.

name	repo-structure
description	Describes the structure of the robotic-autonomy repo — its topic folders, their purpose, and how to create and maintain work-log notes (ddmmYYYY.md format). Use this skill whenever you need to navigate the repo, add new work, or record progress for the day.

Robotic Autonomy — Repo Structure

This repo is a research initiative for building, evaluating, and deploying autonomous robot systems.

Top-level Layout

robotic-autonomy/
├── README.md                    # Project overview, objectives, current work
├── INTERESTING_WORK_NOTE.md     # Scratchpad for random research papers & links
├── agents/                      # Sub-project: agent-bench skill-as-bench framework
├── safety/                      # Sub-project: humanoid safety benchmark (MuJoCo)
└── .pi/skills/repo-structure/   # This skill

Folder Details

`agents/`

Topic: Benchmark-as-skill framework for testing robot agent loops.

Covers work on agent-bench:

New benchmark skills (e.g. maze-bench, navigation tasks)
Raycasted visual input pipeline (PNG → LLM → action)
Expanding the perceive → reason → act → repeat loop
Agent performance analysis and scoring

Work logs go here as date-named files.

`safety/`

Topic: Physics simulation (MuJoCo) stress-testing humanoid robots.

Covers work on the humanoid-safety-benchmark:

Scenario design (falls, trips, power loss, punches, kicks, body slams)
Injury metric implementation and tuning (HIC₁₅, Nij, ISO/TS 15066)
ONNX locomotion policy loading and comparison vs. passive ragdoll
Findings and regressions (e.g. Nij 0.85 in forward-fall scenarios)

Work logs go here as date-named files.

`INTERESTING_WORK_NOTE.md`

Topic: Informal scratchpad for research papers, links, and ideas thrown in on the fly.

Lives at the repo root (not a folder)
No strict format — drop a title, link, and a one-liner on why it's interesting
See the file itself for the running list

Work Log Convention

Every folder uses date-named Markdown files as work logs.

Filename format

ddmmYYYY.md

Part	Meaning	Example
`dd`	Day (zero-padded)	`08`
`mm`	Month (zero-padded)	`04`
`YYYY`	Four-digit year	`2026`

Example for 8 April 2026: 08042026.md

Suggested note template

# <Topic Folder> — 08 Apr 2026

## What I did
-

## Findings / results
-

## Blockers
-

## Next steps
-

Rules

One file per day per folder. If you work across multiple topics in a day, create a log in each relevant folder.
File lives directly inside the topic folder — no sub-directories needed for logs.
Keep logs factual and terse. Bullet points are preferred over prose.
If you reference code, link to the commit or file rather than pasting large snippets.

Adding a New Topic Folder

Create the folder at the repo root with a short, lowercase, hyphenated name.
Add a one-line README.md inside it describing the topic.
Update the layout table in this SKILL.md.
Update the top-level README.md if the topic represents a significant new workstream.