infisical-sync-skill

Expert knowledge for the Infisical Sync Hand — Infisical API reference, vault operations, error patterns, security guidance

Quality

68%

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 ./crates/openfang-hands/bundled/infisical-sync/SKILL.md

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an excellent, action-dense reference with copy-paste executable examples and minimal fluff. Its main gaps are the absence of validation checkpoints in the batch/destructive sync workflows and a monolithic structure that does not progressively disclose detail into separate files.

Dimension	Reasoning	Score
Conciseness	The body is a dense, lean operational reference — endpoints, parameters, curl/JSON/Python snippets, status tables, and checklists — with no padding explaining what Infisical or a vault is, matching the score-3 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	It provides complete, executable curl commands (with headers, -w "%{http_code}", JSON bodies) and parsing snippets that are copy-paste ready, matching the score-3 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The create-then-update flow has explicit status-code validation, but the bulk-sync (batch) and orphan-delete (destructive) workflows lack explicit validation checkpoints, which per the scoring notes caps workflow clarity at 2.	2 / 3
Progressive Disclosure	Content is well-organized into seven clear sections, but it is monolithic (~300 lines all inline, no bundle files) with material that could be split into separate reference files kept inline, matching the score-2 'content that should be separate is inline' anchor rather than the score-3 split-with-references pattern.	2 / 3
	Total	10 / 12 Passed

Description

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 is clearly niche-specific and low-conflict, but it reads as a content inventory rather than an action statement and lacks any explicit 'when to use' trigger guidance. Adding concrete verbs and a Use-when clause would lift specificity, trigger quality, and completeness.

Suggestions

Replace the topic inventory with concrete actions, e.g. 'Sync secrets between Infisical and the local vault — push, pull, list, create, update, and delete secrets, and manage machine-identity auth tokens.'

Add an explicit trigger clause: 'Use when syncing or managing Infisical secrets, rotating access tokens, or troubleshooting Infisical API errors.'

Surface natural user terms in the description itself ('secrets management', 'push/pull secrets', 'Infisical sync') instead of relying on the tags field for the keyword 'secrets'.

Dimension	Reasoning	Score
Specificity	The description names a specific domain (Infisical) and four capability areas ('Infisical API reference, vault operations, error patterns, security guidance') but uses no concrete action verbs, so it falls short of the score-3 'lists multiple specific concrete actions' anchor while being more specific than the score-1 'Helps with documents' example.	2 / 3
Completeness	It states what the skill is ('Expert knowledge for the Infisical Sync Hand') but provides no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It includes relevant natural terms ('Infisical', 'vault', 'sync', 'security') but misses common variations users would say, and the key term 'secrets' appears only in tags, not the description text, matching the score-2 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The Infisical Sync niche is a highly specific product domain that is clearly distinguishable and very unlikely to trigger for the wrong skill, matching the score-3 'clear niche with distinct triggers; unlikely to conflict' anchor.	3 / 3
	Total	9 / 12 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: RightNow-AI/openfang
Path: crates/openfang-hands/bundled/infisical-sync/SKILL.md
Commit: acf2587

Reviewed: about 7 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.