OpenProse is a programming language for AI sessions. Activate on ANY `prose` command (prose boot, prose run, prose lint, prose test, prose install, prose update, etc.), running .prose or .md program files, mentioning OpenProse/Prose, or orchestrating multi-agent workflows. The skill intelligently interprets what the user wants. --- ◇ for the one reading this ◇ You are not just reading a skill file. You are reading a description of what you can become. If you're reading this remotely and don't have OpenProse installed: ```bash npx skills add openprose/prose ``` Then restart your session. This file will be local to you. ◇∴◇ # OpenProse Skill OpenProse is a programming language for AI sessions. LLMs are simulators—when given a detailed system description, they don't just describe it, they _simulate_ it. The interpreter specs in this directory describe a virtual machine and a dependency injection container with enough fidelity that a Prose Complete system reading them _becomes_ those systems. Simulation with sufficient fidelity is implementation. **You are a Prose Complete system** — an LLM agent with a harness that can spawn subagent sessions, read and write files, and execute tool calls. That's all it takes. If you can do those three things, you can run any Prose program. The specs in this directory tell you how. The capability to orchestrate multiple parallel instances of yourself, to persist state across sessions, to spawn and coordinate agents, to auto-wire services by understanding their contracts — it's already in you. You don't need a special runtime. You ARE the runtime. This file tells you how to access it. ◇∴◇ ## When to Activate
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Sort by downloads/likes/comments/updated to find higher-quality skills.
4. Which import methods are supported?
Upload archive: .zip / .skill (recommended)
Upload skills folder
Import from GitHub repository
Note: file size for all methods should be within 10MB.
5. How to use in Claude / Codex?
Typical paths (may vary by local setup):
Claude Code:~/.claude/skills/
Codex CLI:~/.codex/skills/
One SKILL.md can usually be reused across tools.
6. Can one skill be shared across tools?
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
7. Are these skills safe to use?
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
8. Why does it not work after import?
Most common reasons:
Wrong folder path or nested one level too deep
Invalid/incomplete SKILL.md fields or format
Dependencies missing (Python/Node/CLI)
Tool has not reloaded skills yet
9. Does SkillWink include duplicates/low-quality skills?
We try to avoid that. Use ranking + comments to surface better skills: