Name: factorial
Rating: 59.2 (1 reviews)
Author: membranedev

factorial

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

Quality

69%

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

Quality

Content

76%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 highly actionable with executable commands and a clear connection workflow including state-based feedback loops. Its main weakness is the absence of validation steps before running potentially destructive HR actions, which caps workflow clarity.

Suggestions

Add a validation/verification step before running write or destructive actions (e.g. dry-run, confirm affected records, check the response for errors and retry on failure).

Tighten introductory prose (remove the auth-plumbing aside and the platform summary that Claude can infer) to improve token efficiency.

Fix the step numbering inconsistency (a referenced 'Step 2' is unlabeled, and '1b' has no '1a') so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands with brief context, but contains minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' and the introductory platform summary, matching the efficient-with-trimmable-excess anchor.	4 / 5
Actionability	It provides copy-paste-ready executable commands throughout (install, login, connection ensure, action list/run, request) plus a flags table, covering the common cases fully.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with state-based checkpoints and a poll loop, but running Factorial actions on HR data is potentially destructive/batch and lacks validation/verification steps before execution, invoking the cap at 3.	3 / 5
Progressive Disclosure	Content is organized into clear labeled sections with no nested references (no bundle files exist), and most material is appropriately placed inline; it stops short of 5 because the CLI reference and proxy flags are sizeable inline material that a larger skill might split out.	4 / 5
	Total	16 / 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 is third-person, names the specific product, and includes an explicit 'Use when' trigger, giving it solid completeness and distinctiveness. It is held back by generic action verbs and a lack of natural HR-domain trigger terms users would actually say.

Suggestions

Replace generic verbs with concrete HR actions, e.g. 'Manage employee data, payroll, time off, and documents'.

Expand the trigger clause to include natural user phrases: 'Use when the user wants to manage Factorial employees, payroll, time off, or HR records'.

Add the domain synonym 'HR' so the description matches how users naturally refer to the platform.

Dimension	Reasoning	Score
Specificity	Names the Factorial domain plus a few action phrases ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete HR-specific operations like payroll or time off, fitting between the generic-actions anchor (2) and the concrete-actions anchor (3).	3 / 5
Completeness	It states both a what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Factorial data'), matching the anchor where both are present but the trigger could be more specific.	4 / 5
Trigger Term Quality	It surfaces 'Factorial' and 'Factorial data' as keywords, but omits the natural HR-domain terms users would actually say (employee, payroll, time off, HR), so it matches the 'some relevant keywords but missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Factorial product gives it a clear niche with low conflict risk, though the generic action phrasing keeps it just short of the fully-distinct anchor (5).	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/factorial/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.