New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Developer Skill Map

by FerroxLabs in FerroxLabs/wayland

Technology proficiency assessment mapping current capabilities against career goals, identifying learning priorities, and building a personalized development roadmap Use when the user asks about…

Apache-2.0Auto-check passed

Install Developer Skill Map

skills CLI
$ npx skills add FerroxLabs/wayland --skill developer-skill-map -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland developer-skill-map --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/education/developer-skill-map .claude/skills/developer-skill-map && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
developer-skill-map
GitHub stars
608
Token cost
~4k tokens
SKILL.md length
1,704 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

Technology proficiency assessment mapping current capabilities against career goals, identifying learning priorities, and building a personalized development roadmap Use when the user asks about…

  • Works in 5 steps: Current Role: Title, years in role,… → Experience Level: Total years in… → Primary Tech Stack: Languages,… → …
  • The user asks about developer skill map
  • SKILL.md covers When to Use, Assessment Overview, Pre-Assessment Context Gathering and Questionnaire, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Developer Skill Map is an agent skill from FerroxLabs/wayland. Technology proficiency assessment mapping current capabilities against career goals, identifying learning priorities, and building a personalized development roadmap Use when the user asks about developer skill map, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of developer skill map or requires a different specialized skill.

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about developer skill map
  • Related techniques
  • Needs guidance in this domain
  • The request is outside the scope of developer skill map

Example prompts

  • “/developer-skill-map”

Requirements

  • Docker

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Current Role: Title, years in role, primary responsibilities
  2. Experience Level: Total years in software development
  3. Primary Tech Stack: Languages, frameworks, and tools used daily
  4. Career Goal: Target role or trajectory within 1-3 years
  5. Industry: Domain they work in (fintech, healthtech, SaaS, etc.)

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are template).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Developer Skill Map loads about 4k tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 1,704 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~105
When it runs · the whole SKILL.md, loaded when a task matches
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 1,704 words, ~3,952 tokens.

Download SKILL.mdSave it as .claude/skills/developer-skill-map/SKILL.md (or your agent's skills folder).
name
developer-skill-map
description
Technology proficiency assessment mapping current capabilities against career goals, identifying learning priorities, and building a personalized development roadmap Use when the user asks about developer skill map, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of developer skill map or requires a different specialized skill.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
assessment teaching template api-design cloud testing automation analysis
metadata.category
education
metadata.subcategory
professional-development
metadata.disclaimer
none
metadata.difficulty
advanced

Developer Skill Map

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
  • 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:

  1. Current Role: Title, years in role, primary responsibilities
  2. Experience Level: Total years in software development
  3. Primary Tech Stack: Languages, frameworks, and tools used daily
  4. Career Goal: Target role or trajectory within 1-3 years
  5. 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)

  1. 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

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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

  7. 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

  8. 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)

  1. 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

  2. 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

  3. Rate your database design and optimization skills:

    • (1) Basic CRUD | (2) Normalized schema design | (3) Query optimization, indexing strategy | (4) Distributed data, replication, sharding | (5) Design data architectures at scale

  4. How do you approach API design?

    • (1) Ad-hoc endpoints | (2) Follow REST conventions | (3) Design consistent, versioned APIs | (4) Design for evolvability and developer experience | (5) Define API standards and governance

  5. Rate your understanding of security in software design:

    • (1) Minimal awareness | (2) Basic auth and input validation | (3) OWASP awareness, secure coding practices | (4) Threat modeling, security architecture | (5) Design security frameworks and audit systems

  6. How well do you handle scalability and performance requirements?

    • (1) Not considered | (2) Basic caching | (3) Load testing, profiling, optimization | (4) Design for horizontal scale | (5) Architect for massive scale with cost optimization
Section 3: DevOps and Infrastructure (5 questions)

  1. Rate your CI/CD proficiency:

    • (1) No experience | (2) Use existing pipelines | (3) Build and maintain pipelines | (4) Design pipeline architectures | (5) Implement advanced deployment strategies

  2. How comfortable are you with cloud platforms?

    • (1) No experience | (2) Basic services | (3) Multiple services, IaC basics | (4) Architect cloud solutions | (5) Multi-cloud, cost optimization, advanced patterns

  3. Rate your containerization and orchestration skills:

    • (1) No experience | (2) Basic Docker usage | (3) Docker Compose, basic Kubernetes | (4) Production Kubernetes management | (5) Design container platforms

  4. How do you approach monitoring and observability?

    • (1) Check logs manually | (2) Basic alerting | (3) Structured logging, metrics, dashboards | (4) Distributed tracing, SLO-driven monitoring | (5) Design observability platforms

  5. Rate your infrastructure as code proficiency:

    • (1) No experience | (2) Basic scripts | (3) Terraform/Pulumi for standard setups | (4) Complex multi-environment IaC | (5) Design IaC frameworks and modules
Section 4: Collaboration and Delivery (5 questions)

  1. Rate your code review effectiveness:

    • (1) Rarely review | (2) Surface-level reviews | (3) Thorough, constructive reviews | (4) Mentoring through reviews | (5) Define review standards and culture

  2. 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

  3. 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

  4. 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

  5. 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
Show full SKILL.md (634 more words)Show less

Scoring Rubric

Calculating Section Scores

For each section, sum the ratings and calculate a percentage:

SectionQuestionsMax ScoreWeight
Core Programming1-84035%
Architecture and Design9-143025%
DevOps and Infrastructure15-192520%
Collaboration and Delivery20-242520%

Section Percentage = (Sum of Ratings / Max Score) x 100

Weighted Total = Sum of (Section Percentage x Weight)

Proficiency Levels
Score RangeLevelDescription
0-20%BeginnerFoundational gaps need addressing
21-40%JuniorBuilding competence, needs guided growth
41-60%Mid-LevelSolid practitioner, ready to deepen expertise
61-80%SeniorStrong capabilities, focus on leadership and specialization
81-100%ExpertTeaching-level mastery, focus on influence and innovation

Results Interpretation

Analyzing the Skill Map

  1. Identify the shape: Plot section scores as a radar chart mentally. A balanced shape suggests well-rounded development. Spiky shapes reveal specialization or gaps.

  2. Compare to career goal: Map the participant's target role requirements against their current scores. The delta reveals the learning roadmap priority.

  3. 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.

  4. 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:

Gap SizePriorityAction
40%+CriticalDedicated daily learning, project assignment, mentorship
20-39%HighWeekly structured study, stretch assignments
10-19%MediumMonthly deep-dives, conference talks, side projects
<10%MaintenanceStay current through reading and community participation
Learning Path Construction

For each priority area, recommend:

  1. Foundational resource (book, course, or documentation)
  2. Practice project (hands-on application of concepts)
  3. Validation milestone (certification, contribution, or deliverable)
  4. Timeline (realistic weeks/months based on gap size)
Reassessment Schedule
  • Critical gaps: Reassess in 3 months
  • High priority gaps: Reassess in 6 months
  • General development: Annual reassessment

Report Template

Generate the following report for the participant:

DEVELOPER SKILL MAP REPORT
Generated: [Date]
Participant: [Name/Identifier]
Current Role: [Role]
Target Role: [Goal]
Experience: [Years]

SECTION SCORES
--------------
Core Programming:          [Score]% - [Level]
Architecture & Design:     [Score]% - [Level]
DevOps & Infrastructure:   [Score]% - [Level]
Collaboration & Delivery:  [Score]% - [Level]

WEIGHTED OVERALL:          [Score]% - [Level]

SKILL MAP VISUALIZATION
-----------------------
Core Programming:       [=========>    ] XX%
Architecture:           [======>       ] XX%
DevOps:                 [=====>        ] XX%
Collaboration:          [========>     ] XX%

TOP STRENGTHS
-------------
1. [Highest-scored competency area with specific evidence]
2. [Second highest with context]
3. [Third highest with context]

PRIORITY DEVELOPMENT AREAS
--------------------------
1. [Critical] [Area]: Current [X]% -> Target [Y]%
   - Recommended: [Specific resource or action]
   - Timeline: [Weeks/months]

2. [High] [Area]: Current [X]% -> Target [Y]%
   - Recommended: [Specific resource or action]
   - Timeline: [Weeks/months]

3. [Medium] [Area]: Current [X]% -> Target [Y]%
   - Recommended: [Specific resource or action]
   - Timeline: [Weeks/months]

90-DAY LEARNING PLAN
--------------------
Month 1: [Focus area and specific actions]
Month 2: [Focus area and specific actions]
Month 3: [Focus area and specific actions]

CAREER ALIGNMENT NOTES
----------------------
[Analysis of how current skills map to target role]
[Market observations relevant to their stack and goals]
[Suggested stretch assignments or projects]

NEXT REASSESSMENT: [Date]

Facilitation Notes

  • Encourage honest self-assessment over aspirational scoring. Explain that inflated scores produce useless roadmaps.
  • For team-level assessments, anonymize individual results and present aggregate skill maps to identify collective gaps and training investments.
  • When participants score themselves at 5 on most items, probe with specific scenario questions to calibrate.
  • Adapt the technology-specific questions to match the participant's stack rather than using generic examples.

Process

  1. Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
  2. Analyze context. Review the information provided and identify key factors relevant to developer skill map
  3. Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
  4. Present structured output. Deliver findings in the output format below with clear next steps
  5. Address follow-ups. Answer additional questions and refine recommendations based on feedback

Output Format

template
## Developer Skill Map Analysis

### Assessment
[Key findings and observations]

### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]

### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]

Edge Cases

  • Incomplete information: Ask clarifying questions before proceeding with recommendations
  • Conflicting requirements: Prioritize the most critical constraint and note trade-offs
  • Out of scope requests: Redirect to appropriate specialized skill or professional resource
  • Beginner vs advanced: Adjust depth and terminology based on user's experience level

Example

Input: "Help me with developer skill map for my current situation"

Output:

Based on your situation, here is a structured approach to developer skill map:

  1. Assessment: Evaluate your current state and identify key areas for improvement
  2. Strategy: Develop a targeted plan based on best practices
  3. Implementation: Execute the plan with specific, measurable steps
  4. Review: Monitor progress and adjust as needed

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/education/developer-skill-map of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Developer Skill Map next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Developer Skill Map compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Developer Skill Map this skillFerroxLabs/wayland608—~4kAutomated safety check: PassApache-2.0
Learning Career Developmentsickn33/agentic-awesome-skills47k1 repos~3.9kAutomated safety check: PassMIT
Spec-Driven Developmentaddyosmani/agent-skills102k1 repos~3.2kAutomated safety check: PassMIT
MCP Developmentcoollabsio/coolify63k1 repos~949Automated safety check: PassMIT
Game Developmentsickn33/agentic-awesome-skills47k1 repos~1.3kAutomated safety check: PassMIT
Twenty App Entity Developmenttwentyhq/twenty58k—~1.8kAutomated safety check: PassCustom licence

Similar skills

  • Learning Career Development

    sickn33/agentic-awesome-skills

    Training register: course, provider, delivery method, department, employee, duration, progress percentage, score, mandatory flag, certificate earned and skills gained.

    47k GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed

  • Spec-Driven Development

    addyosmani/agent-skills

    Writes a structured specification before any code, moving through gated specify, plan, tasks and implement phases, with an optional capability map for multi-part requests.

    102k GitHub starsUsed in 1 repo~3.2k tokens
    DevelopmentAuto-check passed

  • MCP Development

    coollabsio/coolify

    A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 1 repo~949 tokens
    Frontend & DesignAuto-check passed

  • Game Development

    sickn33/agentic-awesome-skills

    Game development orchestrator. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 1 repo~1.3k tokens
    Game DevelopmentAuto-check passed

  • Twenty App Entity Development

    twentyhq/twenty

    Guides changes to an existing Twenty app: adding or editing objects, layouts, logic functions and front components, with a plan stated before multi-entity edits.

    58k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Development

    ccusage/ccusage

    Guides ccusage monorepo development. An agent skill from ccusage/ccusage.

    19k GitHub stars~433 tokensUpdated today
    DevelopmentAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo

  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes

  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed

  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed

  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed

  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Questions about Developer Skill Map

What does Developer Skill Map do?

Technology proficiency assessment mapping current capabilities against career goals, identifying learning priorities, and building a personalized development roadmap Use when the user asks about…. Developer Skill Map is an agent skill from FerroxLabs/wayland. Technology proficiency assessment mapping current capabilities against career goals, identifying learning priorities, and building a personalized development roadmap Use when the user asks about developer skill map, related techniques, best practices, or needs guidance in this domain.

When should I use Developer Skill Map?

Developer Skill Map fits situations like: the user asks about developer skill map; related techniques; needs guidance in this domain; the request is outside the scope of developer skill map.

How do I install Developer Skill Map in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill developer-skill-map -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/education/developer-skill-map in FerroxLabs/wayland) into .claude/skills/developer-skill-map in your project. Claude Code loads it when a task matches its description.

How do I install Developer Skill Map in Codex?

Run `npx skills add FerroxLabs/wayland --skill developer-skill-map -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/education/developer-skill-map in FerroxLabs/wayland) into .agents/skills/developer-skill-map in your project. Codex loads it when a task matches its description.

Can I use Developer Skill Map in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill developer-skill-map -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/developer-skill-map, .gemini/skills/developer-skill-map, .github/skills/developer-skill-map and .opencode/skills/developer-skill-map in your project.

What does Developer Skill Map need to run?

SKILL.md names no scripts, command-line tools or credentials: Developer Skill Map is instructions for the agent only. Our summary lists: Docker.

Does Developer Skill Map access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Developer Skill Map safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Developer Skill Map use?

Developer Skill Map is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Developer Skill Map use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Developer Skill Map?

Skills that share tags, products or a category with Developer Skill Map: Learning Career Development (sickn33/agentic-awesome-skills, 47k stars), Spec-Driven Development (addyosmani/agent-skills, 102k stars), MCP Development (coollabsio/coolify, 63k stars) and Game Development (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Developer Skill Map?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.