Name: oracle-field-service
Rating: 56.8 (1 reviews)
Author: membranedev

oracle-field-service

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

Quality

65%

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/oracle-field-service/SKILL.md

Quality

Content

65%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 executable CLI commands and a clear connection state machine, but it is padded with a long feature bullet list and a concept intro, and lacks validation checkpoints for destructive action/proxy operations.

Suggestions

Trim the ~60-item feature bullet list and the 'Oracle Field Service is a cloud-based platform...' intro; they restate domain knowledge Claude already has.

Add a validation/verification checkpoint before destructive or batch action runs and proxy requests (e.g. dry-run, confirm parameters, check the output/error field before proceeding).

Move the bulk feature catalog and the full proxy flag table into a separate reference file (e.g. references/actions.md) and link to it from a concise overview.

Dimension	Reasoning	Score
Conciseness	Mostly concrete and command-driven, but the ~60-item flat feature bullet list and the introductory paragraph explaining what Oracle Field Service is add tokens Claude does not need; anchor 3, not 4 due to these padded sections.	3 / 5
Actionability	Commands are copy-paste ready throughout (login, connection ensure, action run, request proxy) with a complete flag table, matching anchor 5 (fully executable, specific examples cover common cases).	5 / 5
Workflow Clarity	A clear install->auth->connect->poll-state-machine->search->run sequence exists with branching on connection state, but running actions and proxy requests can be destructive/batch with no validation or verification checkpoint, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Single file with section headers offers some structure, but the 60-item feature list and full proxy flag table are inlined content that would sit better in separate reference files and no external references are signaled; anchor 3.	3 / 5
	Total	14 / 20 Passed

Description

66%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 names a distinct niche and includes an explicit 'Use when' clause, but the listed actions are generic and the trigger phrasing lacks natural synonyms. Strong on distinctiveness, moderate on specificity and trigger quality.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete OFS-specific verbs, e.g. 'schedule and dispatch field technicians, manage activities and resources, run bulk updates'.

Strengthen the 'when' clause with concrete trigger phrases users would naturally say, e.g. 'Use when the user wants to schedule technicians, manage field-service activities, or query OFS records'.

Add common synonyms or the product's common abbreviations (e.g. OFS, field service) to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Oracle Field Service integration") and 1-2 actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete; fits anchor 3 and not 4 because coverage is not comprehensive.	3 / 5
Completeness	Both a clear 'what' (integration, manage data/records/workflows) and an explicit "Use when the user wants to interact with Oracle Field Service data" 'when' clause are present, but the 'when' could be more specific; anchor 4, not 5 because the trigger is not concrete enough.	4 / 5
Trigger Term Quality	The natural keyword "Oracle Field Service" appears, but the trigger phrase "interact with ... data" is generic with no synonyms or file extensions, matching anchor 3; not 4 because common variations are missing.	3 / 5
Distinctiveness Conflict Risk	"Oracle Field Service integration" is a clear niche with a distinct trigger unlikely to fire for other skills, matching anchor 5 (clear niche, minimal conflict risk).	5 / 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/oracle-field-service/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.