Name: infisical
Rating: 50.4 (1 reviews)
Author: membranedev

infisical

Infisical integration. Manage data, records, and automate workflows. Use when the user wants to interact with Infisical data.

Quality

55%

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/infisical/SKILL.md

Quality

Content

61%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 content is action-dense with executable Membrane CLI commands and a real polling feedback loop for connection setup, but it is dragged down by an unnecessary introductory explanation of Infisical and broken workflow cross-references ('1b' without '1a', a nonexistent 'Step 2'). Fixing the numbering and trimming the preamble would meaningfully raise the score.

Suggestions

Remove or compress the opening paragraph explaining what Infisical is; Claude already knows, and the official-docs link suffices.

Fix the workflow numbering: add the missing '1a' (or relabel), and replace the dangling 'Step 2' references with a real 'Step 2: Search and run actions' section.

Make the 'Popular actions' section actually list popular Infisical actions (e.g. get secret, create secret, create service token) instead of restating the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explains what Infisical is ('a secrets management platform designed for developers and DevOps teams...') and includes light marketing phrasing ('focus on the integration logic rather than auth plumbing') that Claude does not need.	3 / 5
Actionability	It provides concrete, copy-paste-ready `membrane` commands for install, login, connection, action search/run, and proxying with a flag table, with only minor gaps such as unsubstituted CONNECTION_ID placeholders and the vague line 'Use action names and parameters as needed'.	4 / 5
Workflow Clarity	The connection flow has a genuine polling feedback loop with explicit state checks (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but the sequence is incoherent: '1b' appears with no '1a', and multiple lines reference a 'Step 2' section that does not exist.	3 / 5
Progressive Disclosure	As a single self-contained file with no bundle references, it is organized into clear, well-signaled sections (Authentication, Connecting, Searching, Running actions, Proxy, Best practices), with only minor organization gaps such as the thin 'Infisical Overview' bullet list and the 'Popular actions' section that repeats a discovery command instead of listing actions.	4 / 5
	Total	14 / 20 Passed

Description

48%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 has an explicit trigger clause and names a distinct product, but its capability statement is generic and lacks the concrete Infisical-specific actions (secrets, environments, service tokens) that would make it sharply useful. Tightening the 'what' with real Infisical operations would lift specificity and completeness.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Infisical actions such as 'manage secrets across environments, create service tokens, and control access'.

Add natural trigger terms users say, e.g. 'secrets', 'environment variables', or 'service tokens', beyond just the product name.

Make the 'Use when' clause more specific, e.g. 'Use when the user wants to read, create, or rotate secrets and configuration in Infisical'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Infisical integration') but its actions are generic ('Manage data, records, and automate workflows') rather than concrete Infisical-specific operations like managing secrets or environments.	2 / 5
Completeness	An explicit 'Use when the user wants to interact with Infisical data' clause is present, but the 'what' is generic ('Manage data, records, and automate workflows') rather than a clear statement of concrete capabilities.	3 / 5
Trigger Term Quality	'Infisical' is the natural keyword a user would say, and it appears twice, but the description misses common variations and synonyms such as 'secrets', 'environments', or 'service tokens'.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ('Infisical') gives it a clear niche with minimal conflict risk, though the generic verb phrases ('manage data', 'automate workflows') create minor overlap with broader data skills.	4 / 5
	Total	12 / 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/infisical/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.