login-manager

平台登录态管理。约定各平台登录流程（强制有头手动登录）、探活规则、中央 cookie+UA 存储路径约定。仅管 4 个平台（douyin/kuaishou/bilibili/xhs-browse）。

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./crews/main/skills/login-manager/SKILL.md

Quality

Content

88%Weight 40%Scale 1-5

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 commands and an explicit validation-first workflow including feedback loops. It is well-structured but carries a long inline rationale section and references shared implementation files that are not part of the provided bundle.

Suggestions

Confirm the referenced `_shared/check-session.ts` and `_shared/relay-sign.ts` exist in the bundle, or note them as out-of-scope implementation files rather than navigable references.

Consider moving the 背后的原理 rationale into a short reference file (e.g. REFERENCE.md) to keep SKILL.md as a lean overview, since the skill exceeds the simple <50-line threshold.

Dimension	Reasoning	Score
Conciseness	The body is dense and operationally focused with concrete commands and tables rather than padding about concepts Claude already knows. The 背后的原理 section explains non-obvious operational rules (why headed, why no cookie import) but could be trimmed slightly, placing it at anchor 4 rather than 5.	4 / 5
Actionability	Copy-paste-ready commands are given (`camoufox-cli --session <platform> --persistent --headed --json open "<URL>"`, `login-manager --platform <platform>`), with concrete login-page URLs, per-platform cookie fields, storage paths, and an exit-code→agent-action table covering the common cases, matching anchor 5.	5 / 5
Workflow Clarity	A clearly sequenced multi-step workflow (Step 0 display rules → Step 1 open → Step 2 notify/wait → Step 3 export+verify) with explicit validation checkpoints (two-tier liveness, verify-before-commit) and feedback loops (exit 2 no-retry, retain session on failure for manual retry), matching anchor 5.	5 / 5
Progressive Disclosure	Good section structure (支持的平台, 用法, 注意事项, 背后的原理) with content mostly well-placed. However the referenced `_shared/check-session.ts` and `_shared/relay-sign.ts` are mentioned inline as implementation notes and are not present in the bundle (only scripts/export-and-verify.ts exists), a minor organization gap keeping it at anchor 4 rather than 5.	4 / 5
	Total	18 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 is specific and highly distinct thanks to its explicit platform scope and exclusions, but it lacks an explicit 'Use when…' trigger clause, which caps completeness. It uses third-person voice throughout, consistent with the rubric's voice guidance.

Suggestions

Append an explicit trigger clause, e.g. 'Use when a platform among douyin/kuaishou/bilibili/xhs-browse needs login-state setup, liveness probing, or cookie/UA storage — not for twitter/weibo/etc.'

Add natural-sounding synonyms/extensions (e.g. '登录态', 'cookie 导出', '探活/alive 检查') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (平台登录态管理) and several concrete actions — defines login flow (强制有头手动登录), liveness-probe rules (探活规则), and central cookie+UA storage path conventions — plus enumerates the 4 managed platforms. It lists several specific actions but not an exhaustive/comprehensive set, matching anchor 4 rather than 5.	4 / 5
Completeness	The 'what' is clear (manages login state, defines flows/probes/storage paths), but there is no explicit 'Use when...' or equivalent trigger clause — only a scope boundary (仅管4个平台), which is weak implied 'when'. Per the guideline, a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Natural trigger terms present: 登录 (login) and the concrete platform keys douyin/kuaishou/bilibili/xhs-browse that a user would name when needing to log in. Coverage is good but a few natural phrasings (e.g. '登录抖音/登录B站' framing) are absent, so anchor 4 fits better than 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche is stated with explicit enumeration of the 4 managed platforms and an explicit exclusion of all others (其他平台不走本skill — 各平台专属 skill 自管登录), giving minimal conflict risk and matching anchor 5.	5 / 5
	Total	16 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: TeamWiseFlow/xiaobei
Path: crews/main/skills/login-manager/SKILL.md
Commit: 72fd07a

Reviewed: 16 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.