CtrlK
BlogDocsLog inGet started
Tessl Logo

contentking

ContentKing integration. Manage data, records, and automate workflows. Use when the user wants to interact with ContentKing data.

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/contentking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 Membrane commands and a clear connection-state workflow, kept mostly concise and well-structured; the main gaps are a dangling "Step 2" reference and absent verification steps for run/proxy operations.

DimensionReasoningScore

Conciseness

The body is mostly lean command-driven content, with only minor editorial padding (e.g. "so you can focus on the integration logic rather than auth plumbing") and a short introductory paragraph that could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready executable commands throughout (login, connection ensure/get, action list/run, request) plus a full proxy flag table, covering the common cases concretely.

5 / 5

Workflow Clarity

The connection flow is clearly sequenced with state checks and a feedback loop (poll after user action), but references a "Step 2" that is not defined and the action-running section lacks explicit verification of results.

4 / 5

Progressive Disclosure

Single-file content is well-organized into clearly headed sections (Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with an external docs link; no bundle files exist, and the structure is good though all detail lives inline.

4 / 5

Total

17

/

20

Passed

Description

66%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 names the brand and includes a Use-when clause, but describes capabilities generically ("data, records, workflows") without revealing ContentKing's SEO-auditing purpose, weakening specificity and trigger terms.

Suggestions

Replace generic verbs with ContentKing's actual capabilities, e.g. "Audit and monitor website SEO, track issues and alerts, generate reports."

Expand the trigger clause with natural user phrasing: "Use when the user wants to check SEO health, review ContentKing issues/alerts, or monitor website changes."

Mention concrete nouns users say (SEO issues, alerts, segments, reports) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the ContentKing domain and lists a few actions ("Manage data, records, and automate workflows"), but the actions are generic and omit the platform's actual capability (SEO auditing/monitoring), so it falls between the generic-actions anchor and a concrete-actions anchor.

3 / 5

Completeness

Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with ContentKing data") are present, but the "when" clause is generic rather than tied to concrete trigger phrases.

4 / 5

Trigger Term Quality

The trigger "Use when the user wants to interact with ContentKing data" surfaces the brand but lacks natural SEO-related synonyms users would say (SEO auditing, website monitoring, search rankings, issues, alerts).

3 / 5

Distinctiveness Conflict Risk

Naming a specific branded SaaS (ContentKing) with a brand-keyed trigger gives it a clear niche and minimal overlap risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.