Rewrite the skills SDK docs for the 0.7 interface

[karmanyaahm]

The skills docs still describe the 0.6.x API. 0.7 replaced essentially all of it, so a reader following these pages today writes a skill against an interface that no longer exists.

What was wrong

The docs said	0.7
mobility = Interface(InterfaceType.MOBILITY)	mobility: Mobility
image = RobotState(RobotStateType.LAST_MAIN_CAMERA_IMAGE_B64)	image: MainImage
a name property and a guidelines() method	the class name and the class docstring
return "msg", SkillResult.SUCCESS	return "msg" / self.fail(...)
self._cancelled flags and a cancel() on every skill	the framework latches, brakes and reports
odom.pose.pose.position.x	odom.x
move_to_cartesian_pose() returning a bool	move_to() blocking and raising
composition via innate.skills	declared sub-skills — innate.skills no longer exists

The composing-skills page was the worst of it: it documented an import path that was removed and walked through run_routine_demo.py, a shipped skill that no longer ships.

The rewrite

Overview — one rule: annotate what you consume. The class name is the skill name, the class docstring is the agent-facing guidelines, the execute() signature is the parameter schema. A plain annotation is guaranteed inside execute() (the run fails up front if the feed never arrives, with the real per-feed grace — 3 s cameras, 6 s battery, 2 s the rest), and | None makes it best effort. Cancellation is stated as the framework's job, carrying the never-time.sleep rule across from the OS repo.

Robot state — typed values replace the enums, with an odom-vs-pose frame table, because picking the wrong one is the classic bug: odom drifts but never jumps, pose corrects and therefore can.

Body control — the 0.7 arm SDK. Blocking and raising (ArmFailed / ArmUnhealthy), move_to FK-verification with reboot-and-retry, move_by from the measured pose, Waypoint/follow(), block=False + wait(), and the standing grip target — why nothing threads gripper= through a trajectory any more.

Composing skills — rebuilt on declared sub-skills and PhysicalSkill / physical_skills typed refs, the shared cancel latch, and self.skills.run() for dynamic ids. Pre-release warning dropped; the feature shipped.

Introduction — skill packages and <folder>/<name> namespacing, symlinked packs replacing extra_skill_dirs and the ~/skills lane, defining-the-class-is-the-registration, and broken skills staying visible with their load error instead of vanishing.

Plus navigation interfaces, the full-body examples, external services, the policy-defined pages, and the shared interface tables.

Also in here

Two commits on top of the rewrite:

• docs: lead the MARS quickstart with the victory_spin skill — the quickstart's "run custom code" step pointed at the Gmail/IMAP skill, which needs an app password before it does anything. It now leads with a victory_spin you can paste, save and watch move, and links the email skill as the follow-on for reaching off the robot.
• Use real robot naming in SSH examples — the SSH and development-setup pages showed a bare goodbot password and a placeholder hostname. Robots ship as MARS the <N>th, so the real pattern is mars-the-<N>th.local with goodbot<N>.

Scope

Agent pages get mechanical import and type-hint updates only — from innate import Agent, SkillRef, list[SkillRef] — since get_skills() now prefers the class over an id string. The old brain_client.agent_types path still works via its compat shim, so nothing there was broken; a full agents-docs pass is a separate job.

Two renames, both reversible

• physical-skill-examples.mdx is retitled "Full-Body Examples". The old title now collides with PhysicalSkill, which in 0.7 specifically means a trained policy. Path unchanged, so no redirect needed.
• composing-skills.mdx loses "(pre-release)".

docs.json is untouched — same page set, same paths.

Verification

Every API claim checked against innate-os at 0.7.0-rc3: innate/__init__.py, skills/types.py (_feed_specs is the feed table), robot/manipulation.py, robot/mobility.py, robot/head.py, state/*.py, and the shipped skills in workspace/innate_skills/. mint broken-links passes clean.

Before merging

0.7.0 is still at rc3. Merging publishes docs for an API that hasn't tagged yet — worth holding until the release.

Two carried-over tables I did not audit against source: HeadTiltAnglesTable and NavigationUseCasesTable. Both are 0.6-era behavioral claims, low risk, but they're the remaining unverified content.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
innateinc	🟢 Ready	View Preview	Aug 8, 2026, 1:40 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.