orbit-general
Open Orbit briefing skill — selected by the Orbit pipeline when the user has two or more connectors connected. Pulls the past 24 hours of activity from every authenticated connector (GitHub, Linear, Notion, Slack, 飞书, Calendar, Gmail, Drive, Sentry, Vercel, …) and renders a single adaptive bento-grid dashboard at the top of "我的设计". Each connector module picks its own UI form (list, avatar stack, status ring, heatmap, file grid, alert card, …) based on the data shape it returns, so the layout scales as Orbit's connector ecosystem grows. This skill should not be triggered manually — it is invoke
Profile →npx skills add nexu-io/open-design --skill orbit-general --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Orbit General Briefing Cross-connector morning briefing that lives at the top of "我的设计". Pulls the past 24 hours of activity from every authenticated connector and lays them out as one editorial bento dashboard. ## ⚠️ Source-of-truth protocol (read this first) **Step 1.** Open and read the shipped `example.html` in this folder before writing any output. That file is the canonical design — your job is to **reproduce it**, not reinterpret it. **Step 2.** Mirror the example's structure 1:1: - Same DOM hierarchy and class names - Same number and order of sections - Same number of bento modules in the same order - Same connector list (do **not** add or drop connectors) - Same KPI labels, same Top 3 entries, same "people waiting" set - Same footer string - Same `<script>` block at the end (link injection) **Step 3.** You may freshen mock data values (counts, names, times) so they read as "today" — but you must not invent new UI elements, sections, modules, badges, callouts, ribbons, banners, decorations or chrome that aren't already in `example.html`. If a detail is not in the example, it does not belong in your output. **Identity guard.** Treat every person name or handle in `example.
- ⚠️ Source-of-truth protocol (read this first)
- ⚠️ Design system policy
- Canvas tokens (use these exact values)
- Page sections (top to bottom)
- Connector → UI mapping (pick the matching family)
- Fallback heuristics (for unknown connectors)
- Implementation constraints (paired do / don't)
What does the orbit-general skill do?
Open Orbit briefing skill — selected by the Orbit pipeline when the user has two or more connectors connected. Pulls the past 24 hours of activity from every authenticated connector (GitHub, Linear, Notion, Slack, 飞书, Calendar, Gmail, Drive, Sentry, Vercel, …) and renders a single adaptive bento-grid dashboard at the top of "我的设计". Each connector module picks its own UI form (list, avatar stack, status ring, heatmap, file grid, alert card, …) based on the data shape it returns, so the layout scales as Orbit's connector ecosystem grows. This skill should not be triggered manually — it is invoke
How do I install it?
Run `npx skills add nexu-io/open-design --skill orbit-general --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.