Name: servicenow
Rating: 56.8 (1 reviews)
Author: membranedev

servicenow

Service Now integration. Manage Incidents, Problems, Tasks, Users, Groups. Use when the user wants to interact with Service Now 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/servicenow/SKILL.md

Quality

Content

57%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 actionable with real CLI commands and a genuinely good connection-state feedback loop, but it opens with concept padding, inlines a large API reference table without any external file split, and omits verification steps for the record-creating actions. Tightening the intro and adding post-run validation would lift the weaker dimensions.

Suggestions

Remove the opening "ServiceNow is a cloud-based platform..." concept paragraph and the "Use action names and parameters as needed." filler; Claude already knows what ServiceNow is.

Add a verification step after running write actions (e.g. re-fetch the record with get-incident and confirm the returned fields, or check the output for error state) to satisfy the destructive/batch validation expectation.

Move the 20-row Popular actions table into a separate references file (e.g. references/actions.md) and link to it from the body, improving progressive disclosure for the longer-than-50-line skill.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("ServiceNow is a cloud-based platform that provides workflow automation...") explains a concept Claude already knows, and filler like "Use action names and parameters as needed." adds padding, so it sits at "mostly efficient but includes some unnecessary explanation" rather than the lean score-4 anchor.	3 / 5
Actionability	It provides concrete, copy-pasteable commands (install, login, connection ensure, action list/run, request) with documented flags and a real actions table, with only minor gaps like placeholder CONNECTION_IDs and a generic input example, matching the score-4 anchor and just short of fully copy-paste-ready 5.	4 / 5
Workflow Clarity	The connection flow has a strong feedback loop (poll --wait, READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR handling), but the action-execution half that creates and updates live ServiceNow records lacks any validation or verification step, and the destructive/batch cap holds workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist, so the single ~180-line SKILL.md holds everything inline including a 20-row API reference table that could live in a separate file; section headers give some structure, but bulk reference content that should be separate is inlined, fitting score 3 rather than the well-split score 4.	3 / 5
	Total	13 / 20 Passed

Description

73%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 cleanly states what the skill does and when to use it with platform-specific trigger terms, making it distinct and low-conflict. Its main weakness is the single generic verb "Manage" in place of multiple concrete actions, which keeps specificity and completeness just below the top anchors.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "List, create, and update Incidents, Problems, Tasks, Users, and Groups in ServiceNow."

Strengthen the "when" clause with concrete triggers, e.g. "Use when the user wants to query, create, or update ServiceNow tickets, records, or catalog items."

Include common synonyms/extensions users say (e.g. "tickets", "change requests", "CMDB", "sys_id") to round out trigger term coverage.

Dimension	Reasoning	Score
Specificity	Quotes "Manage Incidents, Problems, Tasks, Users, Groups" name the domain and several concrete entity types, but the only action verb is the generic "Manage" rather than multiple distinct concrete actions, matching the score-3 anchor and falling short of score 4's "several specific actions".	3 / 5
Completeness	It answers "what" ("Service Now integration. Manage Incidents, Problems, Tasks, Users, Groups.") and "when" ("Use when the user wants to interact with Service Now data."), but the "when" is generic rather than listing concrete trigger phrases, so it lands at 4 and not 5.	4 / 5
Trigger Term Quality	Natural keywords a user would say appear — "Service Now", "Incidents", "Problems", "Tasks", "Users", "Groups" — giving good coverage, but a few common variations or synonyms are missing, fitting score 4 rather than the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	"Service Now integration" tied to named platform-specific entities (Incidents, Problems, Tasks) carves a clear niche with distinct triggers and minimal conflict risk with other skills, matching the score-5 anchor.	5 / 5
	Total	16 / 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/servicenow/SKILL.md
Commit: f484c82

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