Name: oracle-taleo
Rating: 58.4 (1 reviews)
Author: membranedev

oracle-taleo

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

Quality

67%

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

Quality

Content

68%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 CLI commands and a solid connection workflow, but it loses points for a padded intro and the absence of validation checkpoints before running batch/destructive Taleo actions. Structure is good for a single-file skill with no bundle.

Suggestions

Add a validation/verification checkpoint before running data-modifying actions, e.g. confirm the action's inputSchema and expected output, or run a dry-run QUERY first for destructive operations.

Trim the intro paragraph explaining what Oracle Taleo is and remove the "so you can focus on the integration logic" commentary to improve token efficiency.

Consider moving the detailed clientAction field breakdown and the proxy flag table into a separate reference file to tighten the overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command blocks, but the opening paragraph explains what Oracle Taleo is and lines like "so you can focus on the integration logic rather than auth plumbing" add mild padding Claude does not need, fitting the mostly-efficient-with-some-unnecessary-explanation anchor.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure with --wait polling, action list/run with --input JSON, request with a full flag table), covering the common cases with executable guidance.	5 / 5
Workflow Clarity	The connection flow is sequenced with state-checking feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED), but running actions on Taleo data is a batch/destructive-capable operation with no validation or verification checkpoint, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist, so scoring is on structure alone; the body is organized into clear sections (Install, Auth, Connecting, Searching, Running, Proxy, Best practices) with most content appropriately inline, with only minor organization gaps such as the detailed clientAction breakdown that could live separately.	4 / 5
	Total	15 / 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 is well-formed with third-person voice, a clear niche, and an explicit Use-when trigger, but its action list is generic and trigger-term coverage is thin beyond the product name. Tightening the actions and adding natural synonyms would lift the mid-tier dimensions.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete operations users perform, e.g. "search candidates, manage requisitions, and update applicant records".

Expand the trigger clause with natural phrasings users would say, e.g. "Use when the user wants to query Taleo candidates, requisitions, or applications".

Keep the explicit "Use when..." clause but pair it with concrete trigger nouns (candidates, applications, requisitions) to strengthen completeness.

Dimension	Reasoning	Score
Specificity	Names the domain ("Oracle Taleo integration") and a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete, matching the anchor for domain-plus-1-2-actions without comprehensive coverage.	3 / 5
Completeness	It states both a clear "what" (integration managing data, records, workflows) and an explicit "Use when the user wants to interact with Oracle Taleo data" trigger, but the when-clause is somewhat generic rather than listing concrete trigger phrases, fitting the anchor where both exist but when could be more specific.	4 / 5
Trigger Term Quality	"Oracle Taleo" and "interact with Oracle Taleo data" provide a relevant keyword, but there are no synonyms or natural phrasing variations beyond the product name, matching the anchor with some keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"Oracle Taleo integration" carves out a clear niche tied to a specific product with distinct triggers and minimal overlap risk with other skills, matching the top anchor.	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-taleo/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.