star-office-ui

Star Office UI 一键化 Skill：帮主人快速部署像素办公室看板，支持多 Agent 加入、状态可视化、移动端查看与公网访问。

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./SKILL.md

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete executable commands and a clear sectioned structure, but it is verbose and redundant with an inline changelog, and its workflows lack validation checkpoints. Consolidating duplicate sections and moving the changelog to a reference would materially improve it.

Suggestions

Merge the duplicate guidance (sections 3/10.2 on ASSET_DRAWER_PASS, 4/10.1 on Gemini, 5.3/10.4 on API) into single canonical sections to remove redundancy.

Add an explicit validation checkpoint to the quick-start flow (e.g. curl http://127.0.0.1:19000/health) before telling the user to open or publicly expose the dashboard.

Move the section-10 changelog/update notes into a separate reference file (e.g. references/UPDATE_REPORT.md) and link to it from the overview, and reference the existing security_check.py/smoke_test.py scripts where relevant.

Dimension	Reasoning	Score
Conciseness	Provides actionable commands but is padded with conversational blockquotes ('你可以先和主人说', '然后告诉主人'), redundant sections (3 vs 10.2, 4 vs 10.1, 5.3 vs 10.4), and an inline changelog (section 10) carrying time-sensitive dates, so it 'could be tightened'.	2 / 3
Actionability	Throughout the body it gives fully executable, copy-paste bash commands (git clone, pip install, cp, python3 app.py, set_state.py, cloudflared tunnel, venv setup, export env vars), matching 'fully executable code/commands; copy-paste ready'.	3 / 3
Workflow Clarity	Sequences are clearly numbered (sections 1, 10.5) but the primary startup flow lacks validation checkpoints — it starts the backend and exposes it publicly without a verify step (e.g. curl /health), fitting 'steps listed but validation gaps'.	2 / 3
Progressive Disclosure	Well-sectioned with clear headers, but monolithic: the changelog/update content (section 10, referencing a non-bundled docs/UPDATE_REPORT_2026-03-05.md) is inline rather than in a separate reference, and bundled scripts (security_check.py, smoke_test.py) go unreferenced.	2 / 3
	Total	9 / 12 Passed

Description

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly communicates a distinctive niche and several concrete features, but reads more as a feature pitch than a trigger-oriented skill description: it lacks an explicit 'Use when…' clause and natural trigger variations. Adding a when-to-use clause would lift completeness and trigger_term_quality.

Suggestions

Append a 'Use when...' clause stating the natural user triggers (e.g. 'Use when the user wants to set up or share a pixel office dashboard for AI agents').

Replace marketing phrasing like '一键化 Skill' with concrete third-person action verbs to improve specificity and trigger naturalness.

Add common natural keyword variations a user might actually say (e.g. 'pixel office dashboard', 'agent status board') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities ('部署像素办公室看板', '多 Agent 加入', '状态可视化', '移动端查看', '公网访问'), but these are feature descriptions rather than comprehensive concrete actions, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	Clearly answers 'what' (deploy a pixel office dashboard with listed features) but provides no 'Use when…' trigger or equivalent explicit 'when' guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant domain terms ('像素办公室看板', '公网访问', '多 Agent') but uses marketing phrasing ('一键化 Skill') and lacks common natural variations a user would say, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	Targets a clear, distinct niche ('Star Office UI' pixel office dashboard) with specific triggers unlikely to overlap with other skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ringhyacinth/Star-Office-UI
Path: SKILL.md
Commit: f29c107

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.