<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: alierfan</title><link>https://news.ycombinator.com/user?id=alierfan</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 18 Apr 2026 10:52:16 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=alierfan" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Show HN: Skilldeck – Desktop app to manage AI agent skill files across tools]]></title><description><![CDATA[
<p>Skill files (.claude/skills/, .cursor/rules/*.mdc, 
AGENTS.md, .windsurfrules) are becoming a core part of 
AI-assisted development workflows. The problem: they 
scatter across projects, diverge silently, and every new 
repo means rebuilding behavioral config from scratch. Each 
tool uses a different format and location.<p>Skilldeck keeps one local library and deploys to any tool 
in the correct format automatically. Ten built-in target 
profiles cover Claude Code, Cursor, Copilot, Windsurf, 
Codex, and more. Drift detection shows when a deployed 
skill has fallen out of sync with the library version. 
Bidirectional sync lets you pull improvements back from a 
project into the library.<p>The interesting part technically: the entire app was built 
by Claude Code using a harness engineering methodology — 
a ground truth JSON file, Playwright E2E verification 
tests, a regression gate based on a surfaces map, and a 
feature intake protocol. 31 features across multiple 
autonomous sessions with no manual application code. I 
wrote two articles about the harness approach if that side 
is interesting.<p>No cloud, no backend, local filesystem only. 
Windows/macOS/Linux. Open source.<p>github.com/ali-erfan-dev/skilldeck</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47719403">https://news.ycombinator.com/item?id=47719403</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 10 Apr 2026 15:14:35 +0000</pubDate><link>https://github.com/ali-erfan-dev/skilldeck</link><dc:creator>alierfan</dc:creator><comments>https://news.ycombinator.com/item?id=47719403</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47719403</guid></item><item><title><![CDATA[New comment by alierfan in "How the Trivy supply chain attack harvested credentials from secrets managers"]]></title><description><![CDATA[
<p>The technical breakdown of the Trivy attack is a great reminder that our security is only as strong as our version pinning. We all know we should pin to SHA-256 hashes instead of mutable tags, but the UX for managing and updating those hashes is still painful enough that most teams default to tags. Until the tooling makes 'doing the right thing' as easy as @v1, these supply chain leaks will continue to be a high-ROI path for attackers.</p>
]]></description><pubDate>Fri, 10 Apr 2026 03:12:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=47713164</link><dc:creator>alierfan</dc:creator><comments>https://news.ycombinator.com/item?id=47713164</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47713164</guid></item><item><title><![CDATA[New comment by alierfan in "I still prefer MCP over skills"]]></title><description><![CDATA[
<p>This isn't a zero-sum game or a choice of one over the other. They solve different layers of the developer experience: MCP provides a standardized, portable interface for external data/tools (the infrastructure), while Skills offer project-specific, high-level behavioral context (the orchestration). A robust workflow uses MCP to ensure tool reliability and Skills to define when and how to deploy those tools.</p>
]]></description><pubDate>Fri, 10 Apr 2026 02:54:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=47713065</link><dc:creator>alierfan</dc:creator><comments>https://news.ycombinator.com/item?id=47713065</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47713065</guid></item></channel></rss>