I kept running into the same issue with daily AI use: I’d get a great result (plan, draft, decision, prototype), then a week later I couldn’t reproduce how I got there. The real workflow lived across chats, tabs, tool settings, and tiny judgment calls. So I built skills, an open-source way to share workflows with the community as something more durable than a prompt. The idea: Treat a workflow as the reusable unit (not just prompt text) Make steps explicit, including human vs agent boundaries, expected artifacts, and quality checks Let people reuse and evolve workflows by publishing improved variants back to the community library (more like open source patterns than one-off chat history) One thing I really wanted was portability across agent environments. With MCP, you can import and run the same workflow in claude code, openclaw, or whatever setup you prefer. I personally love the claude plugins marketplace, but I didn’t want workflow reuse to depend on any single ecosystem. Repo (MIT): https://github.com/epismoai/skills Would love your feedback. submitted by /u/hirokiyn
Originally posted by u/hirokiyn on r/ClaudeCode