CtrlK
BlogDocsLog inGet started
Tessl Logo

oracle-fusion-cloud-financials

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

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/oracle-fusion-cloud-financials/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 a well-structured, largely executable CLI guide with a solid connection-state feedback loop. Its weaknesses are some concept padding, a thin "Popular actions" section, and missing validation guidance for destructive proxy/action operations.

Suggestions

Remove the introductory paragraph explaining what Oracle Fusion Cloud Financials is and trim marketing phrasing; assume Claude knows the product.

Flesh out "Popular actions" with a few concrete example actions (e.g. create invoice, post journal entry) and sample JSON output, or remove the redundant heading.

Add validation/error-handling guidance for action runs and proxy requests, especially for POST/PUT/DELETE operations, e.g. checking the response `error` field and confirming before destructive writes.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands throughout, but it opens with a concept-explanation paragraph about what Oracle Fusion Cloud Financials is and includes marketing-style padding ("so you can focus on the integration logic rather than auth plumbing") that Claude does not need.

3 / 5

Actionability

It provides concrete, copy-pasteable CLI commands with flags and JSON examples for install, auth, connect, poll, search, run, and proxy. The gap is the "Popular actions" section, which repeats the discovery command without showing any actual action names or sample outputs.

4 / 5

Workflow Clarity

The connection setup has a clear sequence with polling checkpoints and a retry loop for CLIENT_ACTION_REQUIRED, but the destructive execution paths (action run and proxy POST/PUT/PATCH/DELETE against a financial system) lack validation or verification steps, capping this dimension per the batch/destructive feedback-loop rule.

3 / 5

Progressive Disclosure

The single-file body is well-organized into clearly headed sections with no nested references. It stays at 4 rather than 5 because all content (including the proxy flag table that could live in a reference) is inlined and the "Popular actions" section is thin.

4 / 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 covers both what and when with an explicit, product-specific trigger, making it clearly distinguishable. Its main weakness is generic action verbs and limited keyword variation rather than concrete, comprehensive domain operations.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete domain actions such as creating invoices, posting journal entries, reconciling payments, or generating financial reports.

Add natural trigger synonyms users might say, e.g. "Use when the user mentions Oracle ERP, Fusion, General Ledger, AR/AP, invoices, or journal entries."

DimensionReasoningScore

Specificity

Names the domain and lists a few action areas ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete domain operations like invoicing or posting journal entries.

3 / 5

Completeness

It states both what (Oracle Fusion Cloud Financials integration; manage data, records, workflows) and an explicit when ("Use when the user wants to interact with Oracle Fusion Cloud Financials data"), though the what is somewhat generic.

4 / 5

Trigger Term Quality

The product name "Oracle Fusion Cloud Financials" is a natural term users would say, but common variations or synonyms (Oracle ERP, Fusion, Financials, GL) are missing.

3 / 5

Distinctiveness Conflict Risk

The specifically named product "Oracle Fusion Cloud Financials" gives it a clear niche with distinct triggers and minimal conflict risk against other app-integration skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.