CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

predictingthepast

Ancient text restoration, attribution, dating, contextualization, and embedding via Aeneas (Latin) / Ithaca (Ancient Greek). Use when asked to "restore", "attribute", "date", "contextualize", "find parallels", "where was it written", "when was it written", "embed", or "analyze" an ancient text, inscription, or epigraphic document, or when the user mentions "Aeneas", or "Ithaca".

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

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.

A highly actionable, well-sequenced operating manual with copy-paste commands, explicit pre-flight validation checkpoints, and a properly delegated output-format reference. Main weaknesses are mild redundancy (duplicated citation reminders, overlapping notification rules, dual-platform server blocks) and limited progressive disclosure — the long acknowledgements and platform blocks could be split into reference files.

Suggestions

Merge the duplicate citation/acknowledgement reminders ('first time you return inference results' and 'first time you present inference results') into a single statement, and fold the 'User Notification' prerequisite into the 'Notification' core rule to remove redundancy.

Move the dataset acknowledgements, citations, and the platform-specific HTML-serving blocks into a reference file (e.g. references/acknowledgements.md), keeping SKILL.md a leaner overview with one-level-deep pointers.

Add brief error-recovery guidance (e.g. what to do when preprocessing rejects the input or a restoration constraint is violated) to close the feedback-loop gap in workflow clarity.

DimensionReasoningScore

Conciseness

The body is densely operational (markup table, flag defaults, timing heuristics, license text — all things Claude cannot know), but contains minor trimmable redundancy: the citation reminder appears twice ('first time you return inference results' vs 'first time you present inference results'), the 'User Notification' prerequisite overlaps the 'Notification' core rule, and full parallel Linux and Windows server blocks pad the serving section. This matches the 4 anchor ('minor instances of over-explanation that could be trimmed') rather than 3, since nearly every section carries non-obvious operational content.

4 / 5

Actionability

Commands are copy-paste ready (`uv run <SKILL_DIR>/scripts/preprocess.py --language=latin --input=...`, three inference combinations, dashboard generation) and cover the common cases, with a complete flag reference including defaults and constraints. This matches the 5 anchor ('fully executable; copy-paste ready code or commands; specific examples cover the common cases').

5 / 5

Workflow Clarity

The sequence is clear (prerequisites → first-load markup prompt → preprocessing → pre-flight checks → task selection → inference → presentation) with explicit confirm-with-user checkpoints for restoration complexity and multi-window splitting. It falls short of the 5 anchor because there are no error-recovery feedback loops (nothing instructs what to do if preprocessing rejects the input or inference fails), matching the 4 anchor ('clear sequence with most checkpoints present; minor validation gaps'). No destructive/batch cap applies.

4 / 5

Progressive Disclosure

The body is well-sectioned and delegates the output schema to a clearly signaled, one-level-deep, verified reference ([output_format.md](references/output_format.md)). It is not a 5 because SKILL.md is a ~330-line full operating manual rather than an overview: dataset acknowledgements, citations, and platform-specific server blocks could live in reference files, and the other bundle files in references/ (iphi-*, led-*) are never mentioned in the body. It exceeds the 3 anchor because the one reference that is used is clearly signaled and appropriately placed.

4 / 5

Total

17

/

20

Passed

Description

96%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.

A strong description that names the domain, tools, languages, and all five concrete tasks, paired with an explicit and richly phrased 'Use when' trigger clause covering verbs, natural question forms, and tool names. The only weakness is the generic breadth of 'analyze'/'embed' as triggers, which introduces slight conflict risk with general text-analysis skills.

DimensionReasoningScore

Specificity

The description lists five concrete named actions ("restoration, attribution, dating, contextualization, and embedding") tied to specific tools and languages ("Aeneas (Latin) / Ithaca (Ancient Greek)"), comprehensively covering the skill's task set. This matches the 5 anchor ('multiple specific concrete actions; comprehensive coverage') and exceeds the 4 anchor since there are no noticeable coverage gaps.

5 / 5

Completeness

It explicitly answers both 'what' (five concrete tasks via named models) and 'when' ("Use when asked to ... or when the user mentions 'Aeneas', or 'Ithaca'") with concrete trigger phrases. This is a direct match for the 5 anchor; the explicit 'Use when' clause rules out the 3-anchor cap.

5 / 5

Trigger Term Quality

Trigger terms include natural user phrasings ("restore", "find parallels", "where was it written", "when was it written", "embed", "analyze") plus domain synonyms ("ancient text, inscription, or epigraphic document") and tool names ("Aeneas", "Ithaca"). Coverage is comprehensive, matching the 5 anchor with question-form phrasing that goes beyond the anchor example; it is not a 4 because no common variations are obviously missing.

5 / 5

Distinctiveness Conflict Risk

The epigraphic niche is clear and tool names are distinctive, but the bare verbs "analyze" and "embed" are generic and create minor overlap risk with general text-analysis or embedding skills, matching the 4 anchor ('minor overlap risk with closely related skills'). It does not fit the 5 anchor because those unscoped verbs are not as tightly distinctive as the rest of the triggers.

4 / 5

Total

19

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

google-deepmind/science-skills

Path

skills/predictingthepast/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.