AGENT SKILL
app-publishing
Publish a tested Robium application as a coherent project page, article, and media set.
- License 许可
- MIT
- 所属仓库
- robium-ai/robium
- 最近更新
- 2026-10-07
- Stars
- ★ 108
- Forks
- 2
01 前言 Front Matter
- name
- app-publishing
- description
- Publish a tested Robium application as a coherent project page, article, and media set.
02 资源文件 6
- 参考文档evals.yaml570 B
- 参考文档references/article-starter.md1.5 KB
- 参考文档references/asset-workflow.md2.8 KB
- 参考文档references/editorial-system.md3.3 KB
- 参考文档references/publication-contract.md2.4 KB
- 参考文档references/visual-system.md2.2 KB
03 SKILL.md 正文
App publishing
Let the application and its real runs own the facts; publishing gives those facts one clear public identity.
Start from recorded reality
- Publish only after the application's normal smoke passes. If the story presents a hosted path, its hosted smoke must pass too.
- Read the app manifest, README, architecture record, case study, and run artifacts before changing copy or visuals.
- Keep runtime and capability facts in
robium-app.yaml, article framing and media indocs/case-study.md, and current availability in the website. - Read publication-contract.md when adding metadata, joining app and article records, or deciding which repository owns a field.
Tell one human story
- Lead with the result, tension, or decision that makes this app worth reading. State run conditions next to the claims they qualify.
- Explain the decisions a reader cannot infer from the README. Keep one tested path and leave exhaustive commands and troubleshooting in the app.
- Cover the outcome, decision, important system boundaries, tested path, result, Robium's contribution, and limits without forcing identical public headings.
- Read editorial-system.md for drafting or revising prose, and article-starter.md when creating a portable case study.
Use media honestly
- Real-run media shows what happened. A diagram explains how the pieces connect. Generated art may illustrate a concept but must not resemble or replace application output.
- Preserve the conditions and source record behind captures. Use literal alt text and captions that say whether a frame is simulated, recorded, or live.
- Read asset-workflow.md when preparing the hero, system diagram, social card, motion, or optional conceptual art.
Keep the surfaces coherent
- Overview, Live, Guide, cards, metadata, and source links share one app ID, project identity, navigation, status vocabulary, and visual language.
- Reuse the project shell and lifecycle components. Keep a special robot viewer or result panel in a small adapter until a second consumer proves it belongs in shared code.
- Read visual-system.md when styling project surfaces. Do not leak parent styles into embedded Gradio, Foxglove, Lichtblick, or other tools.
- Route gateway, orchestrator, and cloud runtime mechanics to
live-demo.
Done
- Every public claim traces to repository-owned facts or a scoped real run.
- The application, article, metadata, and media join on one stable identity.
- Overview, Guide, and Live states work on desktop and mobile, including a readable unavailable state.
- Deployment, paid capacity, production enablement, and external publication remain separately authorized actions.
04 同仓库更多 Skills
visualization
Choose between RViz2, Foxglove, Lichtblick, and Rerun to inspect robot behavior.
★ 108
testing
Choose proportional evidence for robotics software before claiming it works.
★ 108
test-assets
Choose and manage reproducible worlds, models, datasets, and recordings for robotics tests.
★ 108
skill-author
Author and structure practical Robium skills without unnecessary context or ceremony.
★ 108
simulation
Choose between Gazebo, Isaac Sim, and MuJoCo and define what the simulation must prove.
★ 108
rviz2
Inspect and debug live ROS 2 robot state with RViz2.
★ 108