product-tech-influence-article

Write a concise, source-backed Chinese WeChat-ready Markdown article that helps raise a product's technical influence from a neutral third-party advisor perspective, but stop without writing when recent evidence is insufficient. Use when the user provides a product name and asks for recent-news-based product influence writing, product technology commentary, product industry interpretation, brand-neutral technical positioning, or a short public-account article saved under the current project's markdown directory.

Quality

73%

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 ./skills/product-tech-influence-article/SKILL.md

Quality

Content

67%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.

A well-structured, actionable procedural skill with a strong evidence-gate validation checkpoint. The main drag on quality is redundancy across the Workflow, Article Shape, and Quality Bar sections and the absence of a complete worked example.

Suggestions

Consolidate the evidence-gate, transition-background, and template-fatuity rules so each is stated once (in the Workflow) and the Quality Bar references rather than repeats them, cutting roughly 10-15 lines.

Add one short worked example article (filled Article Shape) so the expected output format is unambiguous for the common case.

Tighten the 'Judge before writing' step into a concrete checkpoint with explicit pass criteria, mirroring the evidence gate, to remove the soft-guidance gap in the workflow.

Dimension	Reasoning	Score
Conciseness	The body is instruction-dense with no concept padding Claude already knows, but the evidence-gate, transition-background, and template-fatigue guidance is each restated across the Workflow, Article Shape, and Quality Bar sections, so it could be tightened by deduplication.	3 / 5
Actionability	Guidance is concrete and executable for an instruction skill — numeric thresholds (2+ sources, 900-1500 characters, 3-5 headings), an exact filename pattern, a ready return message, and a template skeleton — but it lacks a fully worked example article covering a common case.	4 / 5
Workflow Clarity	The 6-step sequence is clear and the evidence gate is an explicit validation checkpoint with a detailed pass/fail checklist and a defined stop action, but the secondary 'Judge before writing' checkpoint is soft guidance and there is no fix-and-retry recovery loop.	4 / 5
Progressive Disclosure	The body is well organized into Goal, Workflow, Article Shape, and Quality Bar sections with no nested references, and as a self-contained procedural skill it needs no external files; the single monolithic file over 50 lines with some cross-section redundancy keeps it just below the top anchor.	4 / 5
	Total	15 / 20 Passed

Description

78%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.

A strong description that explicitly answers both what it does and when to use it, with multiple natural trigger phrases and a distinctive niche. The main weakness is that it frames only one or two concrete actions rather than a fuller list of capabilities.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Chinese WeChat-ready Markdown article', 'product's technical influence') and two concrete actions ('Write a... article' and 'stop without writing when recent evidence is insufficient'), but does not list multiple specific actions, so it matches the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor.	3 / 5
Completeness	It clearly states what the skill does ('Write a concise, source-backed Chinese WeChat-ready Markdown article...') and explicitly when to use it ('Use when the user provides a product name and asks for...'), with concrete trigger phrases — matching the anchor for explicit what-and-when.	5 / 5
Trigger Term Quality	The 'Use when' clause gives good keyword coverage with five natural request variants ('product influence writing', 'product technology commentary', 'product industry interpretation', 'brand-neutral technical positioning', 'short public-account article'), though a few common phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	The niche (evidence-gated Chinese WeChat product-influence articles saved to the markdown directory) is mostly distinct, but broader triggers like 'product technology commentary' and 'product industry interpretation' carry minor overlap risk with general commentary or research skills.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: digoal/blog
Path: skills/product-tech-influence-article/SKILL.md
Commit: 3b9c83d

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