CtrlK
BlogDocsLog inGet started
Tessl Logo

fa-jobs-to-be-done

Use when the user asks for D&B Finance Analytics workflows such as customer onboarding, credit decisioning, credit limit validation, portfolio risk management, company reports, ownership trees, folder management, or alerts. Use only the D&B Finance Analytics MCP tools for these workflows.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is tight, actionable, and well-sequenced with sensible error-handling checkpoints, scoring at the top anchor on conciseness, actionability, and workflow clarity. Its one real weakness is progressive disclosure: it routes to a fa-skills/references/ tree that is not present in the bundle.

Suggestions

Ship the referenced files under fa-skills/references/ (fa-onboarding-workflow.md, fa-credit-decisioning.md, fa-credit-validation.md, fa-portfolio-management.md, fa-alerts-monitoring.md, fa-plain-language.md) so the routing table resolves to real content, or inline the essential guidance and remove the dangling references.

Reconcile the reference paths: the body uses fa-skills/references/*.md but the bundle has no references/ directory at all — either add the directory or correct the paths to match the actual bundle layout.

Consolidate the single load of fa-plain-language.md (currently mentioned in Route The Request, Output Layer, and Workflow step 2) into one authoritative instruction to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanations Claude already knows; the tool list, routing table, and behaviors each earn their place without padding. Minor repetition of loading fa-plain-language.md across sections is reinforcement rather than fluff, so it stays at the top anchor rather than dropping to 2.

3 / 3

Actionability

Concrete, specific guidance throughout: a routing table mapping intent signals to exact reference file paths, named MCP tools, and explicit directives like 'Retry a failed... tool call once with the same parameters.' No code is expected for an instruction-routing skill, and the guidance is fully actionable.

3 / 3

Workflow Clarity

A clear 5-step numbered Workflow is backed by explicit checkpoints ('confirm the Finance Analytics MCP tools are available... stop rather than fabricating') and a feedback loop ('Retry... once... If a tool still fails, document what was attempted'). This matches the top anchor's clear sequence with validation and recovery, not the checkpoint-missing level 2.

3 / 3

Progressive Disclosure

The routing table and one-level-deep reference signaling are well organized, but the bundle contains no fa-skills/references/ directory — none of the seven referenced fa-*.md files (fa-onboarding-workflow.md, fa-credit-decisioning.md, fa-plain-language.md, etc.) actually exist, so the disclosure structure is broken in practice. It cannot score 3 because the actual bundle structure does not back the references.

2 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 strong across all dimensions: concrete workflow actions, natural trigger terms, explicit what-and-when guidance, and a clearly distinct niche. No changes needed.

DimensionReasoningScore

Specificity

It lists multiple concrete workflows — 'customer onboarding, credit decisioning, credit limit validation, portfolio risk management, company reports, ownership trees, folder management, or alerts' — matching the top anchor for multiple specific concrete actions rather than the partial coverage of level 2.

3 / 3

Completeness

It explicitly answers both what (the enumerated Finance Analytics workflows) and when ('Use when the user asks for...'), with an explicit trigger clause, so it meets the top anchor rather than capping at 2 for a missing 'Use when' clause.

3 / 3

Trigger Term Quality

The terms (credit decisioning, credit limit validation, portfolio risk management, ownership trees, alerts) are natural phrasings a D&B Finance Analytics user would say, giving good coverage rather than the sparse keyword set of level 2.

3 / 3

Distinctiveness Conflict Risk

D&B Finance Analytics is a narrow, well-scoped niche with distinct domain triggers and an explicit tool constraint ('Use only the D&B Finance Analytics MCP tools'), making it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
openai/plugins
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.