Name: digicert
Rating: 60.8 (1 reviews)
Author: membranedev

digicert

DigiCert integration. Manage Certificates, Orders, Users, Organizations. Use when the user wants to interact with DigiCert data.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

65%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.

A well-structured, actionable integration guide built around executable Membrane CLI commands and a thoughtful connection-state workflow. Its main weaknesses are an inlined reference table with no progressive file split and the absence of validation safeguards for the destructive actions it advertises.

Suggestions

Add a validation/confirmation checkpoint before destructive actions (e.g., confirm organization/domain/certificate identifiers with the user before running delete-organization, revoke-certificate, or delete-domain) to lift the workflow-clarity cap.

Move the Popular actions table into a references/ file (e.g. ACTIONS.md) and link to it from a short summary, reducing inline reference bulk and improving progressive disclosure.

Trim the introductory 'what is DigiCert' paragraph or replace it with a one-line context note, and provide at least one run-action example with real DigiCert parameters instead of a generic placeholder payload.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean operational guidance with copy-paste commands and a tight flag reference table; the opening paragraph ("DigiCert is a provider of digital certificates, used to secure online communications...") is mild over-explanation Claude largely does not need, keeping it just below a 5.	4 / 5
Actionability	Concrete, executable commands abound ("npm install -g @membranehq/cli@latest", "membrane connection ensure ... --json", "membrane action run <actionId> --connectionId=CONNECTION_ID --input '{\"key\": \"value\"}' --json"); not a 5 because the run-action example uses a generic placeholder payload rather than a real DigiCert invocation with actual parameters.	4 / 5
Workflow Clarity	The connect flow has a clear state machine with a feedback loop (poll to READY, handle CLIENT_ACTION_REQUIRED then re-poll, surface CONFIGURATION_ERROR), but the Popular actions table exposes destructive operations (delete-organization, revoke-certificate, delete-domain) with no validation/verification step before running them, which caps this dimension at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Section headers give reasonable structure, but the 20-row Popular actions table is inlined API reference that belongs in a separate file and there are no references/ bundle files or one-level-deep pointers, matching the 'content that should be separate is inline' anchor.	3 / 5
	Total	14 / 20 Passed

Description

78%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.

A solid, third-person description that pairs a concrete capability list with an explicit use-trigger and a distinct named niche. It falls just short of the top marks on specificity, trigger variety, and completeness because it relies on one generic verb and a single trigger phrase.

Suggestions

Replace the generic 'Manage' with a few distinct verbs (e.g., 'List, create, revoke, and download certificates; manage orders, users, and organizations') to broaden action coverage.

Expand the trigger clause with concrete variations users might say, e.g. 'Use when the user wants to issue, renew, revoke, or inspect DigiCert certificates and orders.'

Add file-extension or product keywords (e.g., SSL/TLS certificates, .csr) to improve natural trigger term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Certificates, Orders, Users, Organizations" names the domain plus several concrete entities to act on, matching the 'lists several specific actions; minor gaps' anchor; not a 5 because the single verb 'Manage' is generic rather than a diverse set of distinct actions.	4 / 5
Completeness	It explicitly states both the 'what' ("DigiCert integration. Manage Certificates, Orders, Users, Organizations") and the 'when' ("Use when the user wants to interact with DigiCert data"); not a 5 because the 'when' offers a single trigger phrase rather than the multiple concrete triggers the top anchor expects.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with DigiCert data" plus the named objects (Certificates, Orders, Users, Organizations) give good keyword coverage; not a 5 because there is little synonym/variation coverage beyond the brand name and one trigger phrase.	4 / 5
Distinctiveness Conflict Risk	"DigiCert integration" carves out a clear named niche with a distinct brand trigger and minimal overlap risk with other skills, matching the top anchor.	5 / 5
	Total	17 / 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/digicert/SKILL.md
Commit: f484c82

Reviewed: ~18 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.