1kosmos-blockid
1Kosmos BlockID integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1Kosmos BlockID data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill 1kosmos-blockid72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 includes both 'what' and 'when' components with explicit trigger guidance, which is good. However, the capabilities listed are too generic ('manage data, records, automate workflows') and don't convey what 1Kosmos BlockID actually does (identity/authentication platform). The trigger terms rely heavily on users knowing the exact product name without providing related natural language terms.
Suggestions
Replace generic actions with BlockID-specific capabilities like 'authenticate users', 'verify identities', 'manage passwordless login', or 'configure biometric authentication'
Add natural trigger terms users might say: 'identity verification', 'passwordless', 'biometric authentication', 'IAM', 'single sign-on'
| 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 specific to what BlockID actually does - no concrete capabilities like 'authenticate users', 'verify identity', or 'manage credentials' are listed. | 2 / 3 |
Completeness | Has both 'what' (manage data, records, automate workflows) and 'when' (explicit 'Use when the user wants to interact with 1Kosmos BlockID data'), meeting the requirement for explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes '1Kosmos BlockID' which is the product name users might mention, but lacks natural variations or related terms users might say like 'identity verification', 'passwordless authentication', 'biometric login', or 'IAM'. | 2 / 3 |
Distinctiveness Conflict Risk | The '1Kosmos BlockID' product name provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many integration or data management skills. | 2 / 3 |
Total | 9 / 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.
This skill provides solid actionable CLI commands for 1Kosmos BlockID integration with good examples for common operations. However, it includes some unnecessary introductory content, lacks error handling/validation workflows, and could better organize content with references to external documentation for advanced topics.
Suggestions
Remove the introductory paragraph explaining what 1Kosmos BlockID is - Claude already knows this and users reading the skill likely do too
Add validation steps and error handling guidance (e.g., 'If connection fails, check X; if action returns error, verify Y')
Either remove the entity overview bullet list or make it actionable by linking each to specific action examples or documentation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'It helps enterprises verify user identities...') and the entity overview list adds little value without context. However, the CLI commands and examples are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear copy-paste ready examples. Commands include proper flags, JSON output options, and parameter passing syntax. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack explicit validation checkpoints. No feedback loops for error recovery - e.g., what to do if connection fails or action returns an error. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The entity overview list at the top could link to detailed documentation, and advanced proxy usage could be separated. | 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 | |
- 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.