Name: 1k-debug-logging
Rating: 68.8 (1 reviews)
Author: OneKeyHQ

1k-debug-logging

Add or clean temporary OneKey debug console logs with consistent prefixes and safe stringify. Excludes analytics and permanent server logs.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

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

The body is a tight, executable, well-organized single-purpose skill that assumes Claude's competence and provides copy-paste-ready guidance. No changes needed for the content dimensions.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: it shows the prefix, stringify helper, production no-op, and a call-site example without explaining console.log or JSON.stringify. Every token earns its place.	3 / 3
Actionability	Fully executable TypeScript helper plus a concrete call-site example; copy-paste ready with no pseudocode or missing key details.	3 / 3
Workflow Clarity	A simple single-task skill whose single action (create one local helper, use it at call sites, remove before shipping) is unambiguous and well-sequenced via Pattern then Rules; no destructive/batch operation requires a validation checkpoint.	3 / 3
Progressive Disclosure	Under 50 lines with no external bundle files needed and well-organized sections (Pattern, Rules, Related Skills); the Related Skills links are sibling skills one level deep and clearly signaled.	3 / 3
	Total	12 / 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 distinct, but lacks an explicit "Use when..." trigger and has only partial coverage of natural trigger terms. Adding a trigger clause would raise completeness and trigger_term_quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding or removing temporary local debug logs in OneKey code."

Broaden natural trigger terms to include phrases users commonly say, such as "console.log cleanup", "temp logging", or "debug print statements".

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Add or clean temporary OneKey debug console logs with consistent prefixes and safe stringify" names specific mechanisms (consistent prefixes, safe stringify), not just a domain.	3 / 3
Completeness	The "what" is explicit, but there is no "Use when..." clause or equivalent explicit trigger guidance; the exclusion ("Excludes analytics and permanent server logs") gives a boundary but not a trigger, capping completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	"debug console logs" and "debug logs" are natural but narrow; common variations like "console.log cleanup", "logging", "temp logs" are missing, so coverage is partial rather than broad.	2 / 3
Distinctiveness Conflict Risk	Scoped to OneKey debug logs with explicit exclusions (analytics, permanent server logs), giving a clear niche unlikely to trigger the wrong skill.	3 / 3
	Total	10 / 12 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: OneKeyHQ/app-monorepo
Path: .skillshare/skills/1k-debug-logging/SKILL.md
Commit: d71e6b7

Reviewed: about 4 hours 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.