CtrlK
BlogDocsLog inGet started
Tessl Logo

ramp

Fetch and follow Ramp's published agent playbooks inside Paperclip, with mandatory approval gates for spend, incorporation, cards, account setup, and other financial actions.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./packages/skills-catalog/catalog/optional/finance/ramp/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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, actionable governance wrapper with strong workflow clarity and explicit validation checkpoints for risky financial actions. Conciseness and progressive disclosure are strong but have minor room for trimming and would not benefit from file splitting given the intentional design.

DimensionReasoningScore

Conciseness

Lean policy text that assumes competence and avoids explaining Ramp or approval concepts; minor overlap between the approval-gates list and safety rules could be tightened.

4 / 5

Actionability

Provides a copy-paste curl command, an explicit source allowlist, and a concrete approval-payload field list, with only minor gaps in runnable detail for an instruction-only skill.

4 / 5

Workflow Clarity

Numbered 'Before fetching' and 'Typical flow' sequences with explicit validation checkpoints (approval gates, fail-closed, stop-and-escalate) and a gated-actions checklist for destructive financial operations.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and an intentional self-contained design, though it is a single ~80-line file with no file-level split.

4 / 5

Total

17

/

20

Passed

Description

70%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 specific and highly distinctive, clearly scoping a Ramp-in-Paperclip governance wrapper. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger situations (e.g., setting up Ramp, issuing Ramp cards, Ramp spend approvals).

Include a few common synonyms/variants users might say (e.g., 'Ramp virtual cards', 'Ramp onboarding', 'Ramp reimbursements') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the concrete action ('Fetch and follow Ramp's published agent playbooks') and lists several specific gated domains (spend, incorporation, cards, account setup, financial actions), with only minor coverage gaps.

4 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger clause, so per the judging guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('Ramp', 'spend', 'cards', 'account setup', 'incorporation', 'approval gates') with good coverage, though a few common variants are absent.

4 / 5

Distinctiveness Conflict Risk

Tied to a specific product (Ramp) and system (Paperclip) with distinct financial triggers, giving a clear niche and minimal conflict risk.

5 / 5

Total

16

/

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
paperclipai/paperclip
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.