CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

application-form-filler

Fill out job application form fields with context-aware, tailored answers drawn from the candidate's CV and the job description

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/application-form-filler/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable and well-structured, providing concrete per-question-type templates, length calibration, and worked good/bad examples that Claude could not derive on its own. The main gaps are minor redundancy in length guidance and the absence of an explicit answer-validation feedback loop.

DimensionReasoningScore

Conciseness

The body is directive and earns most of its tokens with task-specific formats, word counts, and anti-patterns Claude would not already know; minor redundancy between the per-type length rules and the Length Calibration table keeps it just below fully lean.

4 / 5

Actionability

Each question type ships a concrete fill-in template, explicit rules, word-count targets, and worked ❌/✅ examples, with a copy-paste code-block output format — fully actionable guidance for an instruction-only skill.

5 / 5

Workflow Clarity

'Before Answering' gives a clear gather-inputs sequence with an explicit checkpoint ('If the user hasn't provided a CV or JD, ask for them before writing') and the Output Format is unambiguous, but there is no validation/feedback loop on the produced answer, so it stops short of the explicit-recovery level.

4 / 5

Progressive Disclosure

No bundle files exist; the skill is a single well-sectioned SKILL.md (When to Use, Before Answering, seven typed question sections, Output Format, Length Calibration, Common Mistakes) with clear headers and easy navigation, so it lands at 'good structure' rather than the 5 that requires well-signaled one-level-deep references.

4 / 5

Total

17

/

20

Passed

Description

61%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 clearly third-person, naming the domain and source inputs concretely, but it omits any explicit 'Use when...' trigger clause, which caps completeness at 3 and limits distinctiveness. Adding a concrete trigger phrase would move it firmly into the upper band.

Suggestions

Append a 'Use when...' clause with concrete triggers (e.g. 'Use when the user asks to fill out job application form fields on Greenhouse, Lever, Ashby, or Workday, or mentions application forms, cover questions, or ATS fields').

Include common synonyms such as 'resume', 'cover letter', and 'ATS' to broaden natural trigger coverage.

Consider listing a couple of concrete sub-actions (e.g. 'draft field answers, calibrate length per field type, format as copy-pasteable blocks') to lift specificity toward the multi-action anchors.

DimensionReasoningScore

Specificity

Names the domain ('job application form fields') and one concrete action ('Fill out... with context-aware, tailored answers drawn from the candidate's CV and the job description'), but does not enumerate multiple distinct actions, so it sits at the 1-2 concrete actions anchor rather than the several-actions level above.

3 / 5

Completeness

The 'what' is clear (fill application form fields with tailored answers), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural user phrasing — 'job application form fields', 'candidate's CV', 'job description' — that users would actually say; a few common synonyms (e.g. 'cover letter', 'resume', 'ATS') are missing, keeping it just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The job-application-form niche is clearly distinct from generic writing skills with only minor overlap risk against resume/cover-letter skills; not a 5 because the missing explicit 'when' triggers weaken distinctiveness.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Paramchoudhary/ResumeSkills

Path

skills/application-form-filler/SKILL.md

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.