CtrlK
BlogDocsLog inGet started
Tessl Logo

zhihu-publish

通过 forked camoufox-cli 持久化 session zhihu 在知乎发布文章或回答。知乎无可用公开 API,需通过浏览器操作完成发布。

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./crews/main/skills/zhihu-publish/SKILL.md
SKILL.md
Quality
Evals
Security

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 executable commands, clear sequenced workflows, validation checkpoints, and a strong pitfalls/error-recovery section. Only minor conciseness trimming and optional reference splitting would improve it.

Suggestions

De-duplicate the close-session and fail-first guidance so it appears once rather than in the intro, 必做约束, and error table.

Consider moving the Pitfalls catalog to a references file to keep SKILL.md as a tighter overview.

The optional 公众号导入 section could be trimmed or moved to a reference if token budget is a concern.

DimensionReasoningScore

Conciseness

Mostly lean: concrete commands and selectors with no padding about what Zhihu/browsers are. Minor repetition of the close-session and fail-first guidance across the intro, 必做约束, and error table keeps it from a 5.

4 / 5

Actionability

Fully executable, copy-paste-ready camoufox-cli commands with concrete selectors, eval workarounds, and fill/upload usage covering articles, answers, images, and editing. Placeholders like <标题-ref> are appropriate since refs come from snapshot.

5 / 5

Workflow Clarity

Clear numbered sequences with explicit validation checkpoints ('snapshot 确认发布成功', 'URL 变为文章详情页') and feedback loops via the error-handling table and Pitfalls with workarounds; the 创作声明 step is flagged ⚠️ 发布前必做.

5 / 5

Progressive Disclosure

Single self-contained file (no references/scripts/assets bundle) with well-organized sections and clear headers. Good structure with minor gaps — the Pitfalls and detailed editor workarounds could optionally live in a reference file, but inline placement is reasonable at this length.

4 / 5

Total

18

/

20

Passed

Description

65%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 clearly names the Zhihu-publishing niche and what it does, with low conflict risk, but lacks an explicit 'Use when' trigger clause and only lists two concrete actions. Adding trigger guidance and a fuller action list would raise it.

Suggestions

Add an explicit trigger clause, e.g. '当用户需要在知乎发布文章或回答、或提到知乎创作/投稿时使用'.

Expand the action list to mention editing answers and image upload so specificity is comprehensive.

Include common synonyms ('写回答', '专栏', '投稿') to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain (Zhihu publishing) and two concrete actions ('发布文章或回答') but does not enumerate the broader set of operations the skill actually supports (editing, image upload, import). Matches anchor 3 ('Names domain and 1-2 concrete actions'); not 4 because it does not list several specific actions.

3 / 5

Completeness

Has a clear 'what' (publish articles/answers on Zhihu via browser automation) but no explicit 'Use when...' trigger clause, so per guidelines completeness is capped at 3. The 'when' is only weakly implied by the domain.

3 / 5

Trigger Term Quality

Includes natural user-facing terms ('知乎', '发布文章', '回答') a user would actually say. Not 5 because common synonyms/variations like '写回答', '专栏', '投稿' are absent; not 3 because the core natural phrases are present rather than only jargon.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Zhihu publishing via a specific persistent browser session) with distinct triggers and minimal overlap risk with other skills. More specific than the anchor-4 'PDF and Word' example.

5 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.