Name: oksign
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

oksign

OKSign integration. Manage Documents, Templates, Users, Teams. Use when the user wants to interact with OKSign data.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/oksign/SKILL.md

Quality

Content

57%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 actionable and the connection workflow has genuine error-recovery checkpoints, but it is padded in places, inlines reference material that should live in separate files, exposes destructive actions without verification safeguards, and contains broken 'Step 2' cross-references. It is competent but would benefit from tightening and restructuring.

Suggestions

Add a verification checkpoint before destructive actions, e.g. run check-document-exists and confirm with the user before remove-document, so the action-running workflow is not uncapped.

Move the Popular actions table and proxy flag reference into a separate references file (e.g. ACTIONS.md) and link to it from a concise overview, restoring one-level-deep progressive disclosure.

Fix the broken step references: either label the connection section 'Step 1' and the searching section 'Step 2', or remove the 'skip to Step 2' phrasing so cross-references resolve.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary padding ('so you can focus on the integration logic rather than auth plumbing') and an opening paragraph explaining what OKSign is that could be trimmed.	3 / 5
Actionability	Provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request proxy) with a flag reference table, but no single worked end-to-end example ties the pieces together, leaving a minor gap.	4 / 5
Workflow Clarity	The connection workflow is well-sequenced with a real feedback loop (poll state, handle CLIENT_ACTION_REQUIRED, re-poll), but references to 'Step 2' resolve to no such header and destructive actions (Remove Document) appear with no validation/verification step, which caps this dimension.	3 / 5
Progressive Disclosure	Section headers give reasonable structure, but the 15-row actions table and proxy flag reference are inlined in a single monolithic file with no external references or signaled navigation to deeper material, which is where this content belongs.	3 / 5
	Total	13 / 20 Passed

Description

62%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 covers what and when with appropriate third-person voice and a distinctive brand name, but relies on a single generic verb ('Manage') and a vague trigger clause instead of concrete actions and natural trigger phrases. It is solid but not exemplary.

Suggestions

Replace the generic 'Manage' with concrete actions, e.g. 'Create, retrieve, and remove Documents; list Users and Teams; upload Form Descriptors'.

Expand the 'Use when' clause with concrete trigger phrases users would actually say, e.g. 'Use when the user wants to send a document for signing, retrieve a signed document, or manage OKSign users and templates.'

Add the natural activity terms 'sign', 'signature', and 'e-sign' so the skill triggers on the core intent, not just the brand name.

Dimension	Reasoning	Score
Specificity	Names the OKSign domain and enumerates concrete entities ('Documents, Templates, Users, Teams') but the only action verb is the generic 'Manage', so concrete actions are listed at a minimal level rather than comprehensively.	3 / 5
Completeness	Has both a clear 'what' (OKSign integration managing Documents/Templates/Users/Teams) and an explicit 'when' ('Use when the user wants to interact with OKSign data'), but the trigger clause is generic rather than listing concrete trigger phrases, so it falls short of a 5.	4 / 5
Trigger Term Quality	Includes relevant domain keywords (OKSign, Documents, Templates, Users, Teams) but misses the core natural activity terms a user would say — 'sign', 'signature', 'e-sign' — and any synonyms or file extensions.	3 / 5
Distinctiveness Conflict Risk	'OKSign' is a named product giving it a clear niche with low conflict risk, but the generic 'interact with OKSign data' trigger means it could still overlap with other e-signature skills when a user is non-specific.	4 / 5
	Total	14 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/oksign/SKILL.md
Commit: f484c82

Reviewed: 5 days 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.