Name: 1k-debug-logging
Rating: 67.2 (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

81%

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%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 content is an exemplar of a lean, single-purpose skill: executable code, tight rules, and clean sectioning with no wasted tokens. No changes needed.

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line purpose, a single copy-paste helper, a call-site example, and tight rules, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Provides complete, executable TypeScript (the helper plus a concrete call-site example) that is copy-paste ready and covers the common case.	5 / 5
Workflow Clarity	A simple single-purpose skill whose single action (create one helper, use it at call sites, remove before shipping) is unambiguous, satisfying the simple-skill exception.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references, yet well-organized into Pattern, Rules, and Related Skills sections, meeting the simple-skill bar for a 5.	5 / 5
	Total	20 / 20 Passed

Description

62%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 is specific and well-bounded, with strong distinctiveness from the explicit exclusion clause. Its main weakness is the missing 'Use when...' trigger guidance, which leaves activation intent implicit and caps completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when adding or cleaning up temporary debug console.log calls during local development.'

Include natural trigger synonyms users would say, such as 'debug logging', 'console.log cleanup', or 'debug logs', to broaden activation matching.

Consider naming the file extension or context (e.g. 'in OneKey client code') to sharpen the trigger further.

Dimension	Reasoning	Score
Specificity	Names the domain ('temporary OneKey debug console logs') and several concrete actions ('Add or clean', 'consistent prefixes', 'safe stringify'), with only minor coverage gaps.	4 / 5
Completeness	The 'what' is clear, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	'debug console logs' is a natural phrase a user might say, but common variations like 'logging', 'console.log cleanup', or 'debug logging' are missing.	3 / 5
Distinctiveness Conflict Risk	It carves a clear niche (temporary local debug logs) and explicitly excludes adjacent domains ('Excludes analytics and permanent server logs'), minimizing conflict risk.	5 / 5
	Total	15 / 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
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: 518bbeb

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