Show HN: Skilldeck – Desktop app to manage AI agent skill files across tools
Developer Ali Erfan has released Skilldeck, a desktop application that centralizes the management of AI agent skill files across tools like Claude, Cursor, and Windsurf. As AI coding assistants become daily infrastructure for developers, the lack of any standard for where and how...
According to the GitHub repository maintained by Ali Erfan (username ali-erfan-dev), Skilldeck is a desktop application built to solve one of the quieter but increasingly painful problems in AI-assisted development: the fact that every AI coding tool stores its behavioral configuration files in a completely different place, in a completely different format, with no coordination between them. The project was submitted to Hacker News as a Show HN post and currently sits at 6 stars with 1 fork, reflecting an early but genuine signal of developer interest in this problem space.
Why This Matters
The fragmentation of AI skill files is not a minor inconvenience. It is the kind of infrastructure debt that compounds quietly until it becomes a serious drag on developer productivity, and for enterprise teams running Claude, Cursor, and Windsurf simultaneously across dozens of repositories, the problem is already there. The AI Daily Brief's primer on agent skills pulled 10,699 views on YouTube, which tells you developers are hungry to understand this system, not just use it casually. Tools that solve cross-vendor coordination problems, think package managers in the early 2010s, tend to become deeply embedded in workflows once developers adopt them. Skilldeck is positioning itself at exactly that kind of chokepoint.
Daily briefing from 50+ sources. Free, 5-minute read.
The Full Story
Over the past 18 to 24 months, AI coding assistants have moved from novelty to daily infrastructure. With that shift came extensibility. Anthropic's Claude lets developers store custom skill files in a .claude/skills/ directory structure. Cursor, built by Anysphere, uses .cursor/rules/ with files in the .mdc format. Codeium's Windsurf reads from a .windsurfrules file. Some workflows use a plain AGENTS.md file at the project root. Each of these systems was built independently, with each vendor optimizing for their own architecture and user experience, not for interoperability.
The result is predictable. A developer who uses more than one of these tools, which describes most serious AI-assisted developers today, ends up maintaining multiple parallel copies of essentially the same behavioral instructions. When they improve a rule in Claude, that improvement does not carry over to Cursor. When they start a new project, they rebuild configuration from scratch. Over time, the versions diverge silently, and there is no easy way to audit what instructions are actually running across the full development environment at any given moment.
Skilldeck, released in version 0.1.0 with 96 commits on its master branch, attacks this problem through centralized management. The desktop application provides a single interface where developers can view, edit, and synchronize skills across all their AI tools. The application handles translation between the different file formats each tool expects, so a developer can define a skill once and push it to Claude, Cursor, and Windsurf in the correct format for each. The commit history also shows that Skilldeck itself was co-developed with Claude Opus 4.6, which adds a layer of self-referential interest to a tool designed to manage Claude's skill files.
Beyond synchronization, Skilldeck provides auditing functionality. Developers can see the complete picture of what behavioral instructions are active across every tool and every project in their environment. That kind of visibility matters not just for individual productivity but for security. A rule designed to prevent an AI agent from accessing sensitive data might exist in Claude but be absent from Cursor, creating a gap that no one notices until something goes wrong. Centralized management closes that gap by making omissions visible.
The application is built with Electron, which explains its cross-platform desktop nature, and uses a GitHub Actions release workflow added in the most recent batch of commits. Ali Erfan prepared the 0.1.0 release with updated documentation, app icons for macOS and Windows packaging, and a fix to the skill deletion logic in the skill store, suggesting the project is moving toward a proper public release rather than staying as a developer preview.
Key Details
- Skilldeck was created by developer Ali Erfan and posted to GitHub at github.com/ali-erfan-dev/skilldeck.
- The repository has 6 stars and 1 fork as of the time of this writing.
- The project reached version 0.1.0 with 96 commits across 1 branch and 1 tag.
- The app targets 4 distinct skill file formats:
.claude/skills/,.cursor/rules/*.mdc,AGENTS.md, and.windsurfrules. - The most recent commit was made on April 9, 2026, fixing PostCSS configuration for ESM compatibility.
- Claude Opus 4.6 is listed as a co-author on multiple commits in the repository.
- The AI Daily Brief's YouTube primer on agent skills accumulated 10,699 views, indicating strong and growing developer interest in understanding these systems.
What's Next
The 0.1.0 release infrastructure, including GitHub Actions workflows and platform-specific app icons, suggests Ali Erfan is preparing Skilldeck for broader distribution, likely through GitHub Releases for macOS and Windows installers. Watch for community contributions to expand format support, particularly as newer AI coding tools enter the market with their own skill file conventions. If the project gains traction, the natural next step is a shared skill library or registry where developers can publish and consume community-built skills, similar to how npm packages work for JavaScript.
How This Compares
Skilldeck did not emerge in isolation. A project called Askill, described as a package manager for AI agent skills with built-in AI safety scoring, appeared on Hacker News approximately 58 days before the Skilldeck submission. Askill approaches the same problem from a distribution and safety angle rather than a local management angle, treating skills more like packages to be installed and audited for risk. A separate tool by developer nicholas_pw, focused on AI agent skill translation and refactoring, appeared on Hacker News about 34 days before Skilldeck. The fact that three independent developers converged on related problems within a two-month window is a strong signal that the ecosystem has hit a genuine coordination wall, not just a niche annoyance.
What makes Skilldeck distinct from those adjacent efforts is its focus on the desktop experience and local management layer. Askill is more about the distribution problem. The translation tool is more about format conversion. Skilldeck is trying to be the daily driver, the thing you have open alongside your IDE. That is a harder product position to win, but it is also the one with the deepest potential for workflow integration. For context on how other AI tools and platforms are handling agent configuration, the broader ecosystem is still very much sorting itself out.
The parallel here to package managers is worth taking seriously. Before npm consolidated JavaScript dependency management, developers dealt with ad hoc solutions and vendor-specific conventions that created exactly the kind of compounding fragmentation that skill files are creating now. The developer who builds the equivalent of npm for AI agent skills will have an enormously sticky product. Whether Skilldeck grows into that role or remains a useful utility depends largely on community adoption and whether tool vendors start treating interoperability as a feature rather than a threat. You can follow related AI agents news to track how this space evolves.
FAQ
Q: What is an AI agent skill file and why does it matter? A: An AI agent skill file is a configuration document that tells an AI coding assistant how to behave in specific situations, what rules to follow, what patterns to avoid, and how to handle particular tasks. They matter because without them, every AI session starts from generic defaults. With well-crafted skill files, the AI knows your project's conventions, security constraints, and preferred patterns from the start.
Q: Does Skilldeck work with all major AI coding tools?
A: Skilldeck currently targets 4 skill file formats used by Claude, Cursor, Windsurf, and generic AGENTS.md workflows. It is an early 0.1.0 release, so the list of supported tools will likely grow as the project matures and more developers contribute support for other platforms.
Q: How do I get started with managing AI agent skills across projects? A: You can clone the Skilldeck repository from github.com/ali-erfan-dev/skilldeck and build it locally using its Electron-based setup. For broader context on structuring skills effectively before you manage them, check out the guides section at AI Agents Daily for practical tutorials on agent configuration.
Skilldeck is an early but well-reasoned attempt to solve a problem that only gets worse as AI-assisted development matures and teams adopt multiple tools simultaneously. Whether it becomes the standard solution or simply accelerates the conversation about standardization, it is pointing at exactly the right problem. Subscribe to the AI Agents Daily weekly newsletter for daily updates on AI agents, tools, and automation.
Get stories like this daily
Free briefing. Curated from 50+ sources. 5-minute read every morning.
