1kosmos-blockid
1Kosmos BlockID integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1Kosmos BlockID data.
61
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/1kosmos-blockid/SKILL.mdQuality
Discovery
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 correctly identifies the product domain and includes an explicit 'Use when' clause, which is good. However, the actions described are very generic ('manage data, records, and automate workflows') and could apply to virtually any integration platform. The description would benefit significantly from listing specific 1Kosmos BlockID capabilities and adding more natural trigger terms related to identity/authentication use cases.
Suggestions
Replace generic actions with specific 1Kosmos BlockID capabilities, e.g., 'manage user enrollments, verify biometric authentication, query identity records, configure passwordless login workflows'.
Add natural trigger terms users might say, such as 'identity verification', 'biometrics', 'passwordless authentication', 'BlockID', or 'digital identity'.
Expand the 'Use when' clause with more specific scenarios, e.g., 'Use when the user mentions 1Kosmos, BlockID, biometric authentication, identity proofing, or passwordless login'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (1Kosmos BlockID) and mentions some actions ('manage data, records, and automate workflows'), but these actions are generic and not concrete — 'manage data' and 'automate workflows' could apply to almost any integration. | 2 / 3 |
Completeness | It answers both 'what' (manage data, records, automate workflows for 1Kosmos BlockID) and 'when' (explicitly states 'Use when the user wants to interact with 1Kosmos BlockID data'), satisfying the explicit trigger guidance requirement. | 3 / 3 |
Trigger Term Quality | Includes '1Kosmos BlockID' which is a specific product name users would mention, but lacks natural variations or specific task-related keywords (e.g., identity verification, authentication, biometrics, user enrollment) that users might actually say. | 2 / 3 |
Distinctiveness Conflict Risk | The '1Kosmos BlockID' product name provides some distinctiveness, but the generic actions ('manage data, records, automate workflows') could overlap with many other integration skills. Without more specific capabilities listed, it could conflict with other data management or workflow automation skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with excellent actionability and workflow clarity — the CLI commands are concrete and the connection state machine is well-documented with explicit feedback loops. The main weaknesses are some unnecessary introductory context (explaining what 1Kosmos is) and a monolithic structure that could benefit from splitting detailed reference material into separate files.
Suggestions
Remove the introductory paragraph explaining what 1Kosmos BlockID is and who uses it — Claude doesn't need this context to execute the skill.
The entity overview bullet list (User, Template, Workflow, etc.) provides no actionable guidance; either remove it or link each entity to specific action examples or a reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what 1Kosmos BlockID is and who uses it is unnecessary context for Claude. The overview bullet list of entities without any actionable detail adds little value. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear parameter placeholders and flags documented in a table. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, error states) and feedback loops (poll until ready, handle client actions, then proceed). The headless auth flow also has a clear two-step process with code completion. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting documents, despite being fairly long (~120 lines of substantive content). The entity overview list could link to detailed documentation, and the proxy request section and best practices could be separated for better organization. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- 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.