CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-humanities

Use when writing humanities or social science papers - provides discipline-specific writing guidance

69

Quality

83%

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

77%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 offers concrete, actionable, well-sequenced guidance with a validation checklist, but it is a monolithic single file that re-explains some general academic-writing concepts Claude already knows and does not offload detail into reference files.

Suggestions

Trim general concepts Claude already knows (basic thesis/evidence/argument definitions, the IMRAD contrast) and keep only humanities-specific guidance to improve conciseness.

Move the detailed citation-format examples and phrasing tables into a references/ file linked from the body to enable true progressive disclosure.

Consider adding a brief worked example (e.g., one short paragraph showing objective academic phrasing applied) to make the style guidance even more directly actionable.

DimensionReasoningScore

Conciseness

Most of the content is concrete, discipline-specific guidance (citation formats, academic phrasing, checklists), but general academic-writing concepts like thesis/evidence/argument and the IMRAD comparison are things Claude already knows, so it could be tightened.

2 / 3

Actionability

As an instruction-only skill it gives concrete, copy-paste-ready guidance: real citation-format examples, ✅/❌ phrasing pairs, named argument structures with flow diagrams, and a usable quality checklist, which satisfies actionable guidance without code.

3 / 3

Workflow Clarity

The 章节写作指南 sequences the paper-writing process (绪论 → 文献综述 → 正文 → 结论) and the 六、质量检查清单 provides an explicit validation checklist at the end, matching the anchor for a clear sequence with checklists.

3 / 3

Progressive Disclosure

The body is a single ~150-line file with no bundle references; it is well-sectioned but detailed reference-like material (citation formats, extensive phrasing tables) lives inline rather than being split into one-level-deep reference files.

2 / 3

Total

10

/

12

Passed

Description

90%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 concise, uses an explicit 'Use when' trigger, and carves out a clear niche, though it describes only one broad action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain ('humanities or social science papers') and a single broad action ('provides discipline-specific writing guidance'), but does not list multiple concrete capabilities, matching the anchor for naming a domain and some actions without being comprehensive.

2 / 3

Completeness

It explicitly answers both 'what' ('provides discipline-specific writing guidance') and 'when' via an explicit 'Use when writing humanities or social science papers' clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

Phrases like 'writing humanities or social science papers' are natural terms a user would actually say, giving good coverage of likely trigger language.

3 / 3

Distinctiveness Conflict Risk

The humanities/social-science-papers niche is specific and distinct, with triggers unlikely to fire for unrelated skills, so conflict risk is low.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Norman-bury/research-writing-skill
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.