Name: 1k-defi-module-integration
Rating: 63.2 (1 reviews)
Author: OneKeyHQ

1k-defi-module-integration

App-side OneKey DeFi guide for Earn, native Discovery-hosted Earn, Borrow, Staking, DeFi Portfolio actions, vaults, lending, protocol integrations, ABI-backed operations, native/provider-backed operations, pending transactions, history, route handoffs, risk display, and DeFi regression review.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.skillshare/skills/1k-defi-module-integration/SKILL.md

Quality

Content

81%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 a well-structured, actionable integration guide with a clear workflow and validation gates, and it uses progressive disclosure effectively with a reference map. The main weakness is broken file references (a missing templates/ directory and an incorrect script path) that undermine copy-paste actionability and navigation.

Suggestions

Fix the readiness script path: the command shows `.skillshare/skills/1k-defi-module-integration/scripts/check-readiness.mjs` but the bundled script lives at `scripts/check-readiness.mjs`; align the invocation with the actual bundle layout.

Create the referenced `templates/feature-packet.md` (referenced twice: in the Autonomous Implementation Contract and the Reference Map) or remove the references so navigation is not broken.

De-duplicate the protocol-classification content that repeats across Scenario Router, Default Workflow, and Readiness Drills to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence without explaining basics, but the Scenario Router, Default Workflow, Reference Map, and Readiness Drills overlap in repeated protocol-classification lists that could be tightened, keeping it just below the lean anchor of 5.	4 / 5
Actionability	Concrete commands (the readiness script invocation), named API endpoints (/wallet/v1/portfolio/positions, /earn/v1/defi/build-transaction), and specific reference paths give mostly executable guidance, but the readiness script path (.skillshare/skills/1k-defi-module-integration/scripts/) and the templates/feature-packet.md reference do not match the actual bundle layout, breaking true copy-paste readiness.	4 / 5
Workflow Clarity	The Default Workflow is a clear numbered sequence with an explicit readiness gate ('Do not continue from a failing readiness check'), Hard Stops as checkpoints, and validation lanes via test-map and validation references, satisfying the explicit-validation + feedback-loop anchor.	5 / 5
Progressive Disclosure	The body is a clean overview with a Reference Map table pointing one level deep to nine real reference files, but the repeated references to a non-existent templates/feature-packet.md and the incorrect readiness-script path are navigation defects that keep it below a 5.	4 / 5
	Total	17 / 20 Passed

Description

70%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, rich in natural trigger terms, and clearly distinct, but it lacks an explicit 'Use when...' clause, which caps completeness. Adding a concrete trigger sentence would lift it from good to strong.

Suggestions

Add an explicit 'Use when App code touches Earn, Borrow, Staking, vaults, lending, DeFi Portfolio actions, or protocol-specific DeFi flows.' clause to the description to satisfy the completeness 'when' requirement.

Reframe some of the noun-list items as concrete actions (e.g., 'implement', 'review', 'route') to push specificity toward the comprehensive-actions anchor.

Trim lower-value enumerations (e.g., 'route handoffs, risk display, and DeFi regression review' duplicates surfaces already named) to keep the description tight.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete DeFi surfaces (Earn, Borrow, Staking, vaults, lending, ABI-backed operations, pending, history, route handoffs), but it is a 'guide for' noun-list rather than concrete action verbs, so it does not fully reach the comprehensive-action anchor of 5.	4 / 5
Completeness	It clearly states what the skill covers, but there is no 'Use when...' trigger clause, and per the rubric a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Strong coverage of natural domain terms (Earn, Borrow, Staking, DeFi Portfolio, vaults, lending, pending transactions, history) including multiple surfaces, but a few common user phrasings/synonyms are still absent.	4 / 5
Distinctiveness Conflict Risk	It carves a clear, narrowly-scoped niche (App-side OneKey DeFi module integration) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: OneKeyHQ/app-monorepo
Path: .skillshare/skills/1k-defi-module-integration/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.