CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-sentry

Configure OneKey Sentry and filter events across desktop, mobile, web, and extension.

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 ./.skillshare/skills/1k-sentry/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%

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

The content is action-oriented and well-structured with a verified one-level reference containing a validated workflow, suffering only minor redundancy and a main body that delegates sequencing to the reference.

DimensionReasoningScore

Conciseness

The body is lean and code-first without explaining what Sentry is, but a few details are repeated (basicOptions.ts appears in prose, the task section, and the key-files table), keeping it just below fully lean.

2.5 / 3

Actionability

It provides executable TypeScript snippets, exact file paths, copy-paste-ready filtering patterns, and the referenced file contains runnable code plus a verification command.

3 / 3

Workflow Clarity

The main body delegates the destructive filtering workflow to the reference, which has a clear 4-step sequence with an eslint validation checkpoint; the body itself lists tasks without an explicit sequenced workflow, so it sits between anchors 2 and 3.

2.5 / 3

Progressive Disclosure

A clear overview with a well-signaled one-level-deep reference ("See: references/rules/ignoring-errors.md") that is a real file, with content appropriately split for this simple skill.

3 / 3

Total

11

/

12

Passed

Description

67%

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 distinctive, clearly scoping the skill to OneKey Sentry across four platforms, but lacks an explicit "Use when..." trigger clause and broader natural-language keywords.

Suggestions

Add an explicit "Use when..." trigger clause, e.g. "Use when filtering or ignoring Sentry errors, or configuring OneKey Sentry on desktop, mobile, web, or extension."

Broaden trigger terms to natural user phrasing such as "ignore errors", "error tracking", and "Sentry errors".

Keep the concise third-person voice but combine it with the trigger clause so both "what" and "when" are explicit.

DimensionReasoningScore

Specificity

"Configure OneKey Sentry and filter events across desktop, mobile, web, and extension" names concrete actions (configure, filter events) and enumerates four platforms, matching the anchor listing multiple specific concrete actions.

3 / 3

Completeness

The description answers "what" (configure and filter Sentry events) but has no explicit "Use when..." trigger clause, so "when" is only implied; per the guideline a missing Use-when caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like "Sentry", "events", "filter events", and the platform names are relevant, but common variations a user would naturally say (e.g., "ignore errors", "error tracking", "Sentry errors") are missing.

2 / 3

Distinctiveness Conflict Risk

Tied specifically to "OneKey Sentry" with platform-scoped triggers, giving it a clear niche unlikely to conflict with other skills.

3 / 3

Total

10

/

12

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

relative_links

Relative link issues: 1 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
OneKeyHQ/app-monorepo
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.