CtrlK
BlogDocsLog inGet started
Tessl Logo

bestblogs-explain

Use this skill when the user wants to understand the "why" behind BestBlogs recommendations — view their interest profile summary, see which followed sources are driving their daily brief, or inspect the score breakdown of a specific resource. Triggers include "BestBlogs 为什么推这条 / 看我的画像 / 我关注的源哪些最有价值 / 这篇文章评分多少", "why did BestBlogs recommend this", "which of my followed sources contribute most", "show score for this resource". Invokes the `bestblogs` CLI.

80

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

The body is concise and action-dense, giving executable CLI commands and concrete response shapes rather than abstract instruction, with clear sequencing and error-recovery guidance for a read-only explain skill. Organization is clean and self-contained with no reference sprawl.

DimensionReasoningScore

Conciseness

The body is lean — a primitives table, fields of interest, a compact JSON snippet, error codes, and composition tips — with no explanation of concepts Claude already knows; every section earns its place rather than the padded-but-accurate style of a 2.

3 / 3

Actionability

Provides fully executable commands (e.g. `bestblogs explain profile --json`, `bestblogs explain sources --days 7 --json`, `bestblogs explain score RAW_xxx --json`), a real JSON response shape, and named fields, making the guidance copy-paste ready rather than the pseudocode of a 2.

3 / 3

Workflow Clarity

The 组合建议 section gives an explicit ordered procedure (依次调 profile → sources → 建议) and the 错误处理 section maps 401 and empty-list outcomes to concrete next actions, supplying the error-recovery feedback loop the 3 anchor expects; the operations are read-only explain calls so no destructive/batch validation checkpoint is required.

3 / 3

Progressive Disclosure

Content is self-contained in a single well-sectioned file with no nested references and no monolithic wall of text; with no bundle files needed, the clear 何时使用/原语/动作/错误处理/组合建议 organization satisfies the well-organized-sections expectation for a self-contained skill.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, trigger-rich in both EN and ZH, and explicitly pairs what the skill does with when to use it, all scoped to a distinct product niche. It is a strong, concise description with no notable weaknesses.

DimensionReasoningScore

Specificity

Lists three concrete actions tied to a specific domain — 'view their interest profile summary, see which followed sources are driving their daily brief, or inspect the score breakdown of a specific resource' — matching the anchor for multiple specific concrete actions rather than the partial single-domain coverage of a 2.

3 / 3

Completeness

Opens with an explicit 'Use this skill when the user wants to understand...' clause covering the when, and enumerates the what (profile/sources/score), clearly answering both what and when with explicit triggers.

3 / 3

Trigger Term Quality

Provides natural phrasings users would actually say in both languages (e.g. 'why did BestBlogs recommend this', 'show score for this resource', '为什么推这条 / 看我的画像'), giving good coverage of common variations rather than the sparse keyword set of a 2.

3 / 3

Distinctiveness Conflict Risk

Anchored to a single product and its `bestblogs` CLI with product-specific triggers ('BestBlogs 为什么推这条', '看我的画像'), giving it a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ginobefun/BestBlogs
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.