Name: 1k-cross-platform
Rating: 54.400000000000006 (1 reviews)
Author: OneKeyHQ

1k-cross-platform

Cross-platform development patterns — platform-specific code (.native.ts/.web.ts/.desktop.ts/.ext.ts) and platformEnv usage.

Quality

63%

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

Fix and improve this skill with Tessl

tessl review fix ./.skillshare/skills/1k-cross-platform/SKILL.md

Quality

Content

68%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 lean, well-organized, and actionable with executable TypeScript examples and clear pointers to a single verified reference file. Its main weakness is workflow clarity: cross-platform edits carry real correctness risk but lack an explicit validate-on-each-platform feedback loop, so the checklist reads as advice rather than a gated process.

Suggestions

Turn the checklist into an explicit validate-then-proceed loop, e.g. after writing a platform variant, confirm the bundler resolves the correct file and run/test on each target platform before moving on.

Move the inline 'Platform Considerations' bullets into the reference file to eliminate duplication and tighten the overview further.

Add the import path for the shared storage interface and storage implementations so the runnable example is fully copy-paste complete.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence, leading with a table, tight code samples, and direct guidance ('ALWAYS use platformEnv'), with only minor padding such as the repeated 'Platform Extensions' heading text and the inline 'Platform Considerations' bullets that overlap with the referenced file.	4 / 5
Actionability	It provides executable, copy-paste-ready TypeScript for detection, a multi-file storage example, and a concrete file-structure layout; minor gaps include no import path for the storage examples and the platform-consideration bullets are descriptive rather than runnable.	4 / 5
Workflow Clarity	There is a checklist and clear guidance for what to do, but the skill involves multi-platform edits where correctness depends on resolving the right variant and testing on each target platform; validation checkpoints for verifying the correct file resolved and that it runs on each platform are present only as un-gated checklist items, not as an explicit validate-then-proceed loop.	3 / 5
Progressive Disclosure	SKILL.md is a well-structured overview with clearly signaled, one-level-deep navigation to the verified reference file references/rules/cross-platform.md and a topic list, though the inline 'Platform Considerations' section partly duplicates content that belongs in the reference.	4 / 5
	Total	15 / 20 Passed

Description

57%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 concrete and distinctive, naming specific file extensions and the platformEnv API, but it completely lacks a 'Use when...' trigger clause so Claude has no explicit guidance on when to invoke it. Adding a single explicit trigger sentence would raise completeness substantially.

Suggestions

Add an explicit 'Use when...' clause naming the natural triggers, e.g. 'Use when writing platform-specific code, adding .native.ts/.web.ts/.desktop.ts/.ext.ts variants, or detecting the runtime platform via platformEnv.'

Mention the target platforms in user-natural terms (React Native, Electron, browser extension) alongside the file extensions to broaden trigger-term coverage.

Frame the skill's purpose as a concrete action ('Patterns for writing...') in a single crisp clause so the 'what' reads as an instruction rather than a label.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete specifics — platform-specific file extensions (.native.ts/.web.ts/.desktop.ts/.ext.ts) and the platformEnv API — giving it solid concrete grounding, though it lists mechanisms rather than a comprehensive set of actions.	4 / 5
Completeness	It clearly states what the skill covers but provides no 'Use when...' trigger guidance, and per the judging guideline a missing explicit trigger clause should cap completeness low; the 'when' is entirely absent rather than merely weakly implied.	2 / 5
Trigger Term Quality	It surfaces natural, searchable tokens a user would mention — 'cross-platform development', 'platform-specific code', the file extensions, and 'platformEnv' — though it omits some common synonyms like 'React Native' or 'Electron' spelled out.	4 / 5
Distinctiveness Conflict Risk	The OneKey-specific extensions and platformEnv usage carve out a clear niche that is unlikely to conflict with generic skills, with only minor overlap risk against broader OneKey coding-pattern skills.	4 / 5
	Total	14 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
relative_links	Relative link issues: 1 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 1 deeper-than-1-level	Warning

	Total	13 / 16 Passed

Repository: OneKeyHQ/app-monorepo
Path: .skillshare/skills/1k-cross-platform/SKILL.md
Commit: 3cff1b4

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