Name: fieldpulse
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

fieldpulse

FieldPulse integration. Manage Organizations. Use when the user wants to interact with FieldPulse data.

Quality

63%

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

Quality

Content

63%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 highly actionable with concrete commands and clear connection-flow branching, but carries some non-essential context and keeps a large reference table inline rather than splitting it out. It is a competent skill document with room to tighten and externalize.

Suggestions

Trim background padding (e.g., the FieldPulse industry list and proxy-internal mechanics) to improve token efficiency.

Add a worked create/update example with a real JSON --input payload to close the actionability gap.

Reconcile step numbering — label the 'Step 2' section explicitly or drop the dangling cross-reference.

Move the large popular-actions table into a references/ file and link it from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands, but includes unnecessary context like FieldPulse's target industries ('HVAC, plumbing, and electrical') and internal mechanics ('The URL is normalized to a domain and matched against known apps') that Claude does not need, matching the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	Copy-paste-ready bash commands and a 20-row popular-actions table give concrete executable guidance for common cases, but there is no full worked input example for create/update actions, leaving a minor gap below the 5 anchor.	4 / 5
Workflow Clarity	The connection setup is sequenced with state-based branching and a poll/re-check feedback loop, but step numbering is inconsistent (a referenced 'Step 2' has no matching header, mixing '1b' and named sections), leaving a minor gap below the 5 anchor.	4 / 5
Progressive Disclosure	Sections are well-organized with headers, but the ~180-line document inlines a large actions table and API/proxy reference that could live in separate files, and no external references exist, matching the 'some structure but content that should be separate is inline' anchor.	3 / 5
	Total	14 / 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 correctly answers both what and when in third person and ties to a distinct product niche, but its action coverage and trigger-term breadth are thin. It earns a solid-but-not-strong rating.

Suggestions

List more concrete actions in the description (e.g., 'Manage organizations, customers, jobs, estimates, and invoices') to raise specificity.

Expand the 'Use when...' clause with concrete trigger phrases users would naturally say (e.g., 'Use when the user wants to manage FieldPulse customers, jobs, or invoices').

Add entity-level synonyms to the trigger so it fires on more natural phrasings.

Dimension	Reasoning	Score
Specificity	Names the domain ('FieldPulse integration') plus one concrete action ('Manage Organizations'), but offers no comprehensive list of actions, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	It states what ('FieldPulse integration. Manage Organizations.') and when ('Use when the user wants to interact with FieldPulse data.'), but the 'when' is generic rather than concrete trigger phrases, so it sits below the 5 anchor.	4 / 5
Trigger Term Quality	The only natural keyword is the brand 'FieldPulse' in 'interact with FieldPulse data'; it lacks synonyms or entity-level variations a user might say, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'FieldPulse' is a distinct niche with minimal conflict risk, though the generic 'interact with FieldPulse data' trigger is less precise than the concrete-trigger 5 anchor.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/fieldpulse/SKILL.md
Commit: f484c82

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