A skill is a repeatable capability: the ability to perform an action or produce a result with some degree of reliability.
Writing, solving equations, negotiating, coding, soldering, diagnosing, drawing, teaching, planning and public speaking are all skills, but they differ in domain, complexity, transferability, evidence, practice requirements, decay, dependence on tools and sensitivity to context.
Quick answer: how should skills be categorised?
- Domain: cognitive, physical, social, technical, creative, managerial?
- Complexity: foundational, intermediate, advanced, expert?
- Transfer: narrow, domain-general, cross-domain?
- Evidence: how can performance be observed?
- Mastery: emerging, competent, fluent, expert?
- Frequency: used daily, occasionally, rarely?
- Dependency: what prerequisite knowledge or skills are required?
- Automation: deliberate, fluent, partly automatic?
- Context: how much does performance depend on environment?
- Decay: how quickly does capability deteriorate without use?
This article applies How to Categorise Anything to human and machine-executed capabilities.
1. Separate skill from knowledge
Knowing what to do and being able to do it reliably are related but different states.
2. Separate skill from task
A task is work to complete; a skill is capability applied across many tasks.
3. Separate skill from talent
Initial aptitude may affect learning speed, but skill classification should focus on demonstrated capability.
4. Domain is one axis
Technical, linguistic, mathematical, interpersonal, artistic and operational describe broad skill domains.
5. Some skills cross domains
Planning, explanation, observation and error-checking can support many fields.
6. Transferability needs evidence
A person skilled in one context may not automatically perform equally well in another.
7. Foundational skills enable later skills
Reading fluency, arithmetic, tool handling and basic coding syntax may act as prerequisites.
8. Skill hierarchies should reflect dependency
An advanced skill should depend meaningfully on lower-level capabilities rather than merely sounding more difficult.
9. Difficulty is not prestige
A high-status skill is not automatically more complex than a lower-status one.
10. Complexity can be decomposed
Number of subskills, uncertainty, coordination, speed and judgement can all contribute.
11. Procedural skills involve sequences
Cooking, laboratory work and equipment maintenance often depend on ordered action.
12. Perceptual skills involve discrimination
Recognising patterns, tones, visual defects or diagnostic cues can depend on trained perception.
13. Motor skills depend on physical control
Balance, coordination, timing and precision matter in many manual and athletic skills.
14. Cognitive skills involve transformation of information
Reasoning, modelling, planning, comparing and calculating are examples.
15. Social skills are relational
Negotiation, listening and leadership depend on other people’s responses and context.
16. Creative skills combine generation and judgement
Producing possibilities and selecting among them are often separate subskills.
17. Tool-dependent skills require environment
Programming in one stack, operating one machine or using one instrument may not transfer fully to another.
18. Tool independence can be a separate measure
Underlying principles may persist even when specific interfaces change.
19. Evidence should be performance-based where possible
Self-report and certificates can help, but observed performance usually provides stronger evidence of actual capability.
20. Speed is not the same as mastery
Fast performance can be inaccurate; careful performance can be highly skilled.
21. Accuracy is only one mastery dimension
Efficiency, adaptability, explanation, error recovery and consistency also matter.
22. Fluency reduces cognitive load
Repeated practice can make routine components more automatic, freeing attention for harder judgement.
23. Automation can hide brittle understanding
Someone may perform familiar routines fluently but fail when conditions change.
24. Adaptive skill matters
Experts often recognise when the standard routine no longer fits and can modify it intelligently.
25. Practice frequency affects retention
Some skills remain stable for years; others decay quickly without use.
26. Decay rate deserves classification
Rare emergency skills may require scheduled refresh even if previously mastered.
27. Skill confidence is not skill level
People can be overconfident or underconfident. Measure confidence separately from performance.
28. Certification is not permanent mastery
A credential records achievement under specified conditions and time, not eternal capability.
29. Context can change skill expression
Performance under stress, time pressure, teamwork or unfamiliar equipment may differ from practice conditions.
30. High-stakes skills need stronger evidence
Safety-critical and professional capabilities deserve observed assessment and recency checks.
31. Composite skills contain subskills
Teaching, surgery, engineering design and management combine many lower-level capabilities.
32. Skill maps should avoid double counting
If several composite skills share the same subskill, represent the dependency rather than duplicating the capability record.
33. AI changes skill boundaries
Tools can automate parts of tasks while increasing the value of verification, judgement and orchestration.
34. Human-plus-tool skill can be its own capability
Using a tool effectively is different from possessing the underlying unaided skill.
35. Skill taxonomies drift
New technologies create new skills and make some old ones less central.
36. Skill ownership belongs to people or agents, not roles alone
A job role may require a skill, but actual capability varies among individuals.
37. A practical skill record
- skill ID;
- domain;
- description;
- prerequisites;
- difficulty;
- transferability;
- evidence method;
- mastery level;
- fluency;
- context;
- tool dependence;
- last demonstrated;
- decay risk;
- related tasks;
- version.
38. Skill categories should improve learning or allocation
If classification does not help training, assessment, staffing or task routing, it may be too vague.
39. Skill is capability under conditions
Mastery only has meaning relative to task difficulty, evidence and context.
40. The deeper idea
A skill is not a label on a person. It is a claim about what that person or system can reliably do.
To categorise a skill well is to preserve what can be done, under what conditions, with what evidence, at what level and how reliably that capability survives change.
Final answer
Categorise skills by domain, complexity, transferability, evidence, mastery, frequency, dependency, automation, context and decay. Separate knowledge from capability, credentials from demonstrated performance, and speed from mastery. Link skills to the tasks and conditions in which they are actually used.
