---
id: "claim-skills-require-good-initial-prompting"
type: "claim"
source_timestamps: ["00:09:42", "00:10:18"]
tags: ["limitations", "prompt-engineering"]
related: ["prerequisite-prompt-engineering"]
speakers: ["Nate B. Jones"]
confidence: "high"
testable: true
sources: ["s40-super-prompts"]
sourceVaultSlug: "s40-super-prompts"
originDay: 40
---
# The Catch: Building a Skill Still Requires Excellent Prompting

## Claim

The existence of [[concept-claude-skills]] does **not** eliminate the need for prompt engineering. The catch: to *build* a highly effective skill, the user must still provide clear, unambiguous, and highly detailed instructions during the creation phase.

You must bring:

- Specific business context
- Specific job descriptions
- Specific examples and constraints
- Concrete formatting and tone preferences

> "You still need to prompt well. It does not get you away from prompting well when you do serious work. Prompting well is like giving this massive cool skill package clear direction."

See [[quote-the-catch]].

## Confidence: High (fully validated)

The enrichment overlay confirms this is fully validated: building effective skills demands strong upfront prompting because LLMs cannot infer user-specific details. Quality input → quality output applies to skill creation just as much as to ad-hoc prompting.

## The Restated Insight

Skills do not replace good prompting — they **package** good prompting so you only have to do it once. This is precisely why [[prerequisite-prompt-engineering|foundational prompt engineering]] is listed as a prerequisite for the entire workflow.

## Testable

Yes. Two users — one with strong prompting skills, one without — building skills for the same workflow should produce skills of measurably different quality.