CtrlK
BlogDocsLog inGet started
Tessl Logo

sdas/leg-spec-from-code-oracle

Extract a complete, source-traceable legacy evidence specification for one Oracle Forms module from Forms XML/FMT/FMB/FMX, PLL/PLD, DDL, message catalogues, menus/object libraries, and screenshots. Use for fresh or incremental reverse engineering when the output must preserve every evidenced screen region, tab, field, operation, rule, message, database dependency, provenance locator, uncertainty, and source-supported detail without inventing target requirements, target architecture, target tests, POC assumptions, or implementation decisions.

66

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

Overview
Quality
Evals
Security
Files

Quality

Content

73%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 well-structured, actionable skill body with a clear validated workflow and good external reference handling. Main weaknesses are moderate cross-section repetition and inlined specification detail that could be further externalized.

Suggestions

Consolidate the overlapping prohibitions between 'Non-Negotiable Boundaries', 'Controlled Evidence Rules', and the validation failure list into a single canonical ruleset referenced once.

Move the detailed per-section format rules (e.g., Section 12 column layout, row-size limits) into references/specification-template.md and link to them from the body.

Add one literal, fully-substituted example command run (with sample tenant/project/module values) alongside the templated invocations to lower the barrier to first execution.

DimensionReasoningScore

Conciseness

Dense and free of basic-concept padding, but themes recur across Non-Negotiable Boundaries, Controlled Evidence Rules, and the validation failure list, so it could be tightened.

3 / 5

Actionability

Provides concrete script invocations with flags, exact paths, section formats, and a real screenshot markdown example, but commands use placeholders requiring substitution and no literal end-to-end run is shown.

4 / 5

Workflow Clarity

A clearly sequenced 7-step workflow with an explicit validation checkpoint (guard + git diff --check) and a fix-then-re-run feedback loop for a controlled-evidence write operation.

5 / 5

Progressive Disclosure

Six real reference files and scripts are clearly signaled one level deep under 'Required References' with bulk template/contract content externalized, though the body still inlines sizable specification detail that could live in references.

4 / 5

Total

16

/

20

Passed

Description

87%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, specific description that clearly answers both what it does and when to use it within a well-defined niche. It could be improved by diversifying the action verbs beyond extract/preserve and adding a few more natural user-facing trigger phrases.

DimensionReasoningScore

Specificity

Names the domain and comprehensive source/output types (Forms XML/FMT/FMB/FMX, PLL/PLD, DDL, message catalogues, menus/object libraries, screenshots) but the action set is essentially two verbs (extract, preserve) rather than many distinct concrete actions.

4 / 5

Completeness

Clearly states both what (extract a source-traceable evidence specification for one Oracle Forms module from listed sources) and when ('Use for fresh or incremental reverse engineering when the output must preserve...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage with natural niche terms and file extensions plus a 'Use for...' clause, but the phrasing is conditional/technical and a few common synonyms (modernization, migration) are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a tight, specific niche (Oracle Forms module evidence extraction) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents