Liam Walsh reacted on this
This is a continuation of my last post on creating Skill (markdown) files in Copilot Cowork to create internal role documentation (responsibilities, skills, skill proficiencies, and qualifications by job family, level, and career stage).
Today, I’ll describe the reference files needed for the original skill files to work correctly.
For example, /role-extraction was the skill I created that extracts role information from a SME’s M365 signals, with prompts at each step for the SME to verify or correct what it finds. The SME knows the role deeply and the skill guides the SME to review the outputs, correct any misconceptions, surface gaps early, and package outputs in a consistent format for my team.
The workflow itself has 7 steps
1. Intake (job family, levels, documents to prioritize)
2. Look for M365 patterns in recent files, recent meetings and transcripts, teams chats, and emails. Surface 4-7 recurring work themes and provide evidence
3. Role and level mapping - draft relevant content, referencing the leveling guidance
4. Responsibility generation - draft 2-3 statements per topic, referencing the writing guidance
5. Skill mapping - identify skills necessary for doing the work, referencing our skills library and identify skill proficiencies needed, referencing our skill proficiencies
6. Qualifications - prompt the SME about the minimum a person needs to perform the role at a baseline level (BQs) and the differentiators that would make them more effective (PQs), referencing the qualification guidance
7. Packaging and delivery - name the file {job family - level - SME name - date.xlsx}, referencing the output schema, and directly email it to the internal Talent Architecture team
As you could see in those steps, there were a lot of additional markdown files to reference, including:
/leveling-framework - defines levels and calibration dimensions (scope, autonomy, impact, complexity) across our three career tracks.
/qualifications - includes our template by level for basic and preferred qualifications, with differences for sponsored and non-sponsored roles. It also runs 4 “tests” that all BQ/PQ must pass
/writing-standards - our canonical standards for writing responsibility statements, which includes length, naming guidance, descriptors, drafting cues, DO/DO NOT rules, etc.
/proficiency-scale - describes our 5-point proficiency scale with definitions of each scale point along with description of whether the skill is “needed day one” or can be learned on the job
/output-schema - describes what I want on each of 7 tabs of the excel file
Skill Library (Excel file) - includes our list of ~1000 maintained skills and skill definitions that we use consistently across the enterprise. We typically are looking to attach 12-15 (but no more than 20) skills per job family
Let me know what else would be interesting for me to share about this process or what you’ve learned if you have tried anything similar.