Dependencies
Task Breakdown
- Create
_data/skills.yml by converting all skills from specs/consolidate-skills/LinkedIn_Skills.md into YAML format with category keys
- Validate YAML parses correctly:
ruby -ryaml -e "YAML.load_file('_data/skills.yml')"
- Update
AGENTS.md to add a reference to _data/skills.yml as the canonical skill vocabulary
- Update
specs/consolidate-skills/spec.md references from LinkedIn_Skills.md to _data/skills.yml
- Update
specs/consolidate-skills/design.md references from LinkedIn_Skills.md to _data/skills.yml
- Update
specs/consolidate-skills/skill-mapping.md references from LinkedIn_Skills.md to _data/skills.yml
- Delete
specs/consolidate-skills/LinkedIn_Skills.md
Notes for the Agent
- The original file has a formatting inconsistency:
TOOLS & TECHNOLOGIES is missing the ## markdown prefix. Ignore this when converting – just use the content.
- Use snake_case for YAML keys:
industry_knowledge, tools_and_technologies, interpersonal_skills
- Keep skills as simple string arrays under each category key
- Preserve the exact skill strings (e.g.,
Python (Programming Language), Amazon Web Services (AWS)) – do not rename or reformat them