Name: officient
Rating: 64.8 (1 reviews)
Author: membranedev

officient

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

Quality

78%

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

Quality

Content

86%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 a well-structured, highly actionable guide with copy-paste commands, a clear connection-lifecycle workflow including state-polling validation, and clean single-file organization. Its only real weakness is mild context-padding in the opening overview paragraph and some explanatory prose.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean bash commands and a flag table without explaining what a CLI or HTTP method is; minor over-explanation (the opening "Officient is an HR platform..." paragraph and some prose around connection states) keeps it just below the fully lean anchor 5.	4 / 5
Actionability	Provides copy-paste-ready, executable commands covering the common cases — install, login, connection ensure, action list/run with JSON params, and proxy requests with a full flag table — matching anchor 5's fully executable standard.	5 / 5
Workflow Clarity	Clear sequence (install → login → ensure connection → poll for READY → search/run actions → proxy fallback) with an explicit validate-fix-retry loop on connection states (re-poll after CLIENT_ACTION_REQUIRED, handle CONFIGURATION_ERROR), satisfying anchor 4; it lacks the explicit checklist/feedback-loop polish of anchor 5.	4 / 5
Progressive Disclosure	A self-contained, single-file skill with no need for external references and clean, clearly-labeled one-level section headers; per the simple-skill guidance this matches anchor 5's well-organized, easy-to-navigate structure with no nested references.	5 / 5
	Total	18 / 20 Passed

Description

70%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 clearly names a distinct niche (Officient) with an explicit "Use when..." trigger, so it answers both what and when. Its main weakness is generic action language ("manage data, records") rather than concrete HR operations, which limits specificity and trigger-term richness.

Suggestions

Replace generic actions with concrete HR capabilities, e.g. "manage employee data, absence, payroll, time off, and expenses" to lift specificity toward anchor 5.

Add natural user-facing trigger terms and synonyms like "HR data", "employee records", or "payroll" so the skill matches more of what users actually say.

Tighten the "when" clause with concrete triggers, e.g. "Use when the user wants to query or update Officient employee, absence, or payroll data."

Dimension	Reasoning	Score
Specificity	Names the domain and 1-2 generic actions ("Manage data, records, and automate workflows") but no concrete HR-specific operations like payroll, absence, or time off, matching anchor 3 rather than the comprehensive coverage of anchor 4-5.	3 / 5
Completeness	Explicitly answers both "what" ("Officient integration. Manage data, records, and automate workflows") and "when" (an explicit "Use when..." clause), satisfying anchor 4; the "what" is generic enough to fall short of anchor 5's concrete comprehensive phrasing.	4 / 5
Trigger Term Quality	Includes the natural trigger phrase "Use when the user wants to interact with Officient data" plus the distinctive "Officient" keyword, but misses common variations a user might say ("HR data", "employee records", "payroll"), placing it just above anchor 3.	4 / 5
Distinctiveness Conflict Risk	Targets a distinct niche via the repeated "Officient" trigger, giving it clear separation from generic skills with only minor overlap risk, matching anchor 4.	4 / 5
	Total	15 / 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/officient/SKILL.md
Commit: f484c82

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