1kosmos-blockid
1Kosmos BlockID integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1Kosmos BlockID data.
68
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/1kosmos-blockid/SKILL.mdQuality
Discovery
57%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 benefits from naming the specific product (1Kosmos BlockID) and including an explicit 'Use when' clause, which gives it structural completeness. However, the actual capabilities described are extremely vague and generic—'manage data, records, and automate workflows' could describe almost any integration tool. The description would be significantly improved by listing concrete BlockID-specific actions and including natural trigger terms related to identity management.
Suggestions
Replace vague actions with specific 1Kosmos BlockID capabilities, e.g., 'enroll users, verify biometric identity, manage authentication policies, query audit logs'.
Add natural trigger terms users would say, such as 'identity verification', 'passwordless authentication', 'biometric enrollment', 'digital identity', or 'MFA'.
Expand the 'Use when' clause with specific scenarios, e.g., 'Use when the user needs to manage identity verification, configure passwordless authentication, or query BlockID enrollment records'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The actions listed are extremely vague: 'manage data', 'records', and 'automate workflows' are generic phrases that could apply to virtually any integration. No concrete actions specific to 1Kosmos BlockID are mentioned (e.g., enroll users, verify identity, manage authentication policies). | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows for 1Kosmos BlockID) and 'when' (Use when the user wants to interact with 1Kosmos BlockID data), with an explicit 'Use when' clause. Though the content is vague, the structure is complete. | 3 / 3 |
Trigger Term Quality | It includes the product name '1Kosmos BlockID' which is a strong trigger term for users who know the product. However, it lacks natural keywords users might say like 'identity verification', 'biometric authentication', 'passwordless login', or other domain-specific terms. | 2 / 3 |
Distinctiveness Conflict Risk | The '1Kosmos BlockID' product name provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with many other integration skills. Without specific BlockID capabilities, it could conflict with other data management or workflow automation skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid, actionable CLI commands for integrating with 1Kosmos BlockID via Membrane, making it practically useful. However, it includes unnecessary introductory context about what BlockID is, and the entity overview list adds no actionable value. The workflow could benefit from explicit validation checkpoints between steps and clearer error recovery guidance.
Suggestions
Remove the introductory paragraph explaining what 1Kosmos BlockID is and the bare entity bullet list — Claude doesn't need this context, and the list has no actionable guidance attached.
Add explicit validation checkpoints between workflow steps, e.g., verify connection status after `membrane connect` before proceeding to action discovery.
Include a brief error recovery flow for failed connections or authentication issues, not just for action creation polling.
| 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, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, polling, and running actions with input parameters. Each command includes concrete flags and placeholders. | 3 / 3 |
Workflow Clarity | The multi-step workflow (install → authenticate → connect → discover → create/run) is present and sequenced, but lacks explicit validation checkpoints. For example, there's no step to verify the connection succeeded before searching actions, and the action creation polling loop doesn't include error recovery guidance beyond checking the error field. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the overview entity list is a wall of unexplained bullet points that adds no navigational value. There are no references to external files for advanced topics, though the external docs link is provided. The skill is borderline monolithic for its length. | 2 / 3 |
Total | 9 / 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
56d7336
- 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.