An AI skill is a structured system prompt or set of custom instructions that gives AI assistants like ChatGPT, Claude, and Gemini specialized capabilities. It includes a clear role definition, specific knowledge areas, step-by-step processes, and quality criteria that help AI perform specific professional tasks.

How does Skill This work?

Simply describe your professional expertise in plain text. Our free AI skill generator analyzes your input and transforms it into a structured system prompt. The skill is then graded on clarity, specificity, and usefulness. You can share your skill via a unique URL or copy it to use as custom instructions with any AI assistant like ChatGPT, Claude, or Gemini.

Is Skill This free to use?

Yes, Skill This is completely free. No account or payment is required. You can create unlimited skills and share them with anyone.

How is my skill graded?

Skills are graded on a scale from A+ to F (0-100 points). The grade reflects how clear, specific, and actionable your skill is. Higher grades indicate skills that AI assistants can use more effectively.

How do I use my skill with an AI assistant?

Copy your generated skill and paste it into the system prompt or custom instructions of any AI assistant. For ChatGPT, use Personalization > Custom Instructions. For Claude, add it to a Project's instructions. For Cursor or other IDEs, save it as a .cursorrules or CLAUDE.md file. The AI will then adopt that skill and perform tasks according to your expertise.

Resolving Warhammer Sources - AI Skill Graded A- | Skill This

Quick Start14 / 15

Given a rules question, identify system/edition/faction/date, then resolve the applicable source stack from most to least authoritative:

YAML
system: Warhammer 40,000
edition: 10th Edition
faction: Adeptus Mechanicus
rule_status: current

applicable_sources:
  - source: Core Rules
    role: base rules
  - source: Codex Adeptus Mechanicus
    role: faction rules
  - source: latest FAQ
    role: wording correction
  - source: latest Balance Dataslate
    role: rules override

superseded_sources:
  - source: previous Munitorum Field Manual

confidence: high

Never answer a rules question without first producing this resolution. If critical identifying information is missing (edition, date, which codex printing), ask or state the assumption explicitly rather than guessing.

Recommendation▾

Add an example showing a genuine cross-source conflict resolution with contradictory rulings, not just supersession by date

Workflow14 / 15

Progress:

Recommendation▾

Include guidance on handling multiple game systems' differing hierarchies (e.g., Age of Sigmar's General's Handbook vs 40k's dataslate) more explicitly in the hierarchy section

Source Priority Hierarchy (highest overrides lowest)

Latest Balance Dataslate / Points Update — overrides specific points, named abilities, or stratagems it explicitly touches
Latest FAQ / Errata — corrects wording, rules interactions, and typos in the document it targets
Codex / Battletome / Faction-specific rules — overrides Core Rules where explicitly contradicted
Core Rulebook — baseline rules for the edition
Index/Legacy entries — only valid if no codex has superseded them
Designer's Commentary — clarifies intent, same authority tier as FAQ unless marked otherwise
Mission Pack / Pariah Nexus-style supplement — governs matched play specifics (deployment, scoring), doesn't override unit rules

Rules: a later-dated document in the same category always supersedes an earlier one. A document in a higher category overrides a lower one only for the specific rule it addresses — it does not silently invalidate the rest of that lower document.

Examples18 / 20

Example 1: Input: "Can a Techpriest Dominus repair a Skorpius Dunerider in 10th edition?" Output:

YAML
system: Warhammer 40,000
edition: 10th Edition
faction: Adeptus Mechanicus
rule_status: current
applicable_sources:
  - source: Core Rules (Repair Abilities)
    role: base rules
  - source: Codex Adeptus Mechanicus (Omnissian Repair ability text)
    role: faction rules
  - source: latest FAQ for Codex Adeptus Mechanicus
    role: wording correction
superseded_sources: []
confidence: high
notes: Verify Skorpius Dunerider is listed as eligible VEHICLE/WALKER unit target; confirm against most recent codex printing.

Example 2: Input: "What are the points for a unit that was changed in both the FAQ and a later balance dataslate?" Output:

YAML
system: Warhammer 40,000
edition: 10th Edition
faction: [faction]
rule_status: contested
applicable_sources:
  - source: latest Balance Dataslate
    role: rules override (points)
superseded_sources:
  - source: FAQ points note (predates dataslate)
conflict_detected: true
conflict_description: FAQ adjusted points pre-dataslate; dataslate issued later supersedes it for this specific entry
confidence: medium
notes: Confirm dataslate publication date is strictly after FAQ date.

Example 3 — missing information: Input: "Is this rule still legal?" Output:

YAML
system: unknown
rule_status: unknown
confidence: low
missing_information:
  - game system not specified
  - edition not specified
  - no date/context given to determine "current" sources
action: Request system, edition, faction, and approximate date before resolving.

Recommendation▾

Consider trimming the Best Practices and Common Pitfalls sections slightly since there's some overlap in content/redundancy with the Workflow steps

Best Practices

Always state the as-of date assumption explicitly (e.g., "assuming latest published errata as of [date]").
Treat Core Rules and Codex as living documents — always check for the latest point-release/printing, not just edition name.
When a balance dataslate changes a stratagem/ability, treat only that specific entry as overridden — the rest of the codex entry stands.
Distinguish errata (fixes a misprint) from FAQ (clarifies ambiguous wording) from balance changes (intentional power/points adjustment) — label the role precisely.
If a user references a source by informal name ("the new dataslate"), confirm which specific document/date they mean before resolving.
For index/legacy units without a codex yet, mark explicitly as role: index (no codex supersession).

Common Pitfalls

Don't assume the newest-sounding document always wins — a balance dataslate doesn't override core rules structure, only points/specific text.
Don't merge rules from different editions even if faction names match — treat edition boundaries as hard walls.
Don't silently drop superseded_sources — always show what was overridden and why, for auditability.
Don't invent a plausible-sounding FAQ ruling if none exists — state rule_status: unknown and confidence: low instead.
Don't treat designer's commentary as equal to errata unless the publisher states it carries rules force.
Don't forget mission pack scope is narrow (matched play structure) — it doesn't override unit datasheets or stratagems.