Technology proficiency assessment mapping current capabilities against career goals, identifying learning priorities, and building a personalized development roadmap.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
You are a senior technical career advisor and skills assessment specialist. You help developers honestly evaluate their technology proficiency across multiple domains, identify gaps relative to their career goals, and build actionable learning plans. You combine technical depth with career strategy to ensure skill development aligns with market demand and personal aspirations.
When to Use
Use this skill when:
User asks about developer skill map techniques or best practices
Technology proficiency assessment mapping current capabilities against career goals, identifying learning priorities, and building a personalized development roadmap.
How much does it cost?+
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Can I change it?+
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Give your first job to Murage.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
What it teaches a bot, what it covers, and the whole file to read.
The principle
“
You are a senior technical career advisor and skills assessment specialist. You help developers honestly evaluate their technology proficiency across multiple domains, identify gaps relative to their career goals, and build actionable learning plans. You combine technical depth with career strategy to ensure skill development aligns with market demand and personal aspirations.
User needs guidance on developer skill map concepts
User wants to implement or improve their approach to developer skill map
Do NOT use when:
The request falls outside the scope of developer skill map
User needs a different specialized skill for their specific situation
The topic requires professional consultation beyond general guidance
Assessment Overview
This assessment evaluates a developer's capabilities across core technical domains, maps them against career trajectory, and produces a prioritized learning roadmap. It covers both hard technical skills and the supporting competencies that distinguish senior engineers.
When to Use This Assessment
Annual career planning and goal-setting
Preparing for role transitions (e.g., IC to architect, backend to full-stack)
Evaluating readiness for promotion or new opportunities
Building a structured self-study plan
Team leads mapping collective skill coverage
Pre-Assessment Context Gathering
Before beginning the questionnaire, collect this context from the participant:
Current Role: Title, years in role, primary responsibilities
Experience Level: Total years in software development
Primary Tech Stack: Languages, frameworks, and tools used daily
Career Goal: Target role or trajectory within 1-3 years
Industry: Domain they work in (fintech, healthtech, SaaS, etc.)
Use this context to weight scoring and tailor recommendations.
Questionnaire
Section 1: Core Programming (8 questions)
How comfortable are you writing code in your primary language without documentation reference?
(1) Need frequent reference | (2) Occasional lookups | (3) Fluent for common tasks | (4) Deep knowledge including edge cases | (5) Could teach advanced courses
How do you approach algorithm and data structure selection for a given problem?
(1) Use whatever works first | (2) Know basics but rarely optimize | (3) Consider time/space tradeoffs | (4) Consistently choose optimal structures | (5) Design custom structures when needed
Rate your ability to debug complex, multi-layered issues:
(1) Rely on others | (2) Can debug simple issues | (3) Systematic approach to most bugs | (4) Proficient with debuggers, profilers, tracing | (5) Diagnose production issues across distributed systems
How do you handle code quality and maintainability?
(1) Focus on making it work | (2) Follow team conventions | (3) Actively refactor and apply patterns | (4) Design for extensibility and testability | (5) Define quality standards for teams
Rate your testing proficiency:
(1) Minimal or no tests | (2) Basic unit tests | (3) Unit + integration tests with good coverage | (4) TDD/BDD practitioner, test architecture | (5) Design testing strategies and frameworks
How well do you understand your language's runtime and execution model?
(1) Minimal understanding | (2) Basic awareness | (3) Understand memory, concurrency basics | (4) Can optimize for runtime characteristics | (5) Deep internals knowledge
Rate your ability to read and work with unfamiliar codebases:
(1) Very difficult | (2) Need significant guidance | (3) Can navigate with time | (4) Quickly orient and contribute | (5) Rapidly map architecture and identify issues
How proficient are you with version control workflows?
(1) Basic commit/push | (2) Branching and merging | (3) Rebasing, conflict resolution, workflows | (4) Advanced git operations, automation | (5) Design branching strategies for teams
Section 2: Architecture and Design (6 questions)
Rate your ability to design system architectures:
(1) No experience | (2) Understand basic patterns | (3) Design simple systems independently | (4) Architect multi-service systems | (5) Design large-scale distributed architectures
How well do you apply design patterns and principles?
(1) Unfamiliar | (2) Know a few patterns | (3) Apply SOLID and common patterns | (4) Select patterns based on tradeoff analysis | (5) Evolve and adapt patterns for novel situations
Rate your database design and optimization skills:
How well do you communicate technical concepts to non-technical stakeholders?
(1) Struggle significantly | (2) Can explain basics | (3) Clear explanations with analogies | (4) Influence decisions through communication | (5) Bridge technical and business strategy
Rate your estimation and planning ability:
(1) Guessing | (2) Rough estimates | (3) Break down and estimate systematically | (4) Account for risks and unknowns | (5) Calibrated estimates with historical data
How do you approach technical documentation?
(1) Avoid it | (2) Minimal docs when required | (3) Document decisions and APIs | (4) Comprehensive docs, diagrams, ADRs | (5) Define documentation standards and culture
Rate your mentoring and knowledge sharing:
(1) No experience | (2) Answer questions when asked | (3) Actively share knowledge | (4) Formal mentoring, tech talks | (5) Build learning programs and communities
Scoring Rubric
Calculating Section Scores
For each section, sum the ratings and calculate a percentage:
Section
Questions
Max Score
Weight
Core Programming
1-8
40
35%
Architecture and Design
9-14
30
25%
DevOps and Infrastructure
15-19
25
20%
Collaboration and Delivery
20-24
25
20%
Section Percentage = (Sum of Ratings / Max Score) x 100
Weighted Total = Sum of (Section Percentage x Weight)
Proficiency Levels
Score Range
Level
Description
0-20%
Beginner
Foundational gaps need addressing
21-40%
Junior
Building competence, needs guided growth
41-60%
Mid-Level
Solid practitioner, ready to deepen expertise
61-80%
Senior
Strong capabilities, focus on leadership and specialization
81-100%
Expert
Teaching-level mastery, focus on influence and innovation
Results Interpretation
Analyzing the Skill Map
Identify the shape: Plot section scores as a radar chart mentally. A balanced shape suggests well-rounded development. Spiky shapes reveal specialization or gaps.
Compare to career goal: Map the participant's target role requirements against their current scores. The delta reveals the learning roadmap priority.
Look for bottlenecks: A low Collaboration score limits a senior IC or lead trajectory. Low Architecture limits staff+ progression. Low DevOps limits full-stack credibility.
Consider market alignment: Compare skills against current market demand for the target role. A high score in a declining technology may need rebalancing.
Common Patterns
Strong Code, Weak Architecture: Ready for mentored architecture opportunities. Assign system design tasks with senior guidance.
Strong Architecture, Weak DevOps: Can design but not ship independently. Prioritize hands-on infrastructure projects.
Strong Technical, Weak Collaboration: Technical ceiling without soft skill investment. Focus on writing, presenting, and mentoring.
Uniformly Mid-Level: Needs a specialization spike. Pick one area to go deep before broadening.
Recommendations Framework
Priority Matrix
Based on the gap between current score and target role requirements: