oss-publish
oss-publish - OSS Publication And Release Hygiene
Focus: make a repository publishable and releasable with minimal ambiguity. Prefer safe-by-default, non-interactive, repeatable steps.
Baseline Repo Artifacts
Add these at repo root (or confirm they exist and are correct):
LICENSE(pick one; do not invent a custom license)README.md(project intent, quick start, examples)CONTRIBUTING.md(how to contribute; local dev workflow)CODE_OF_CONDUCT.md(community expectations; adopt a standard template)SECURITY.md(vulnerability reporting process)- Optional:
SUPPORT.md(where to ask questions)
If the project is a CLI/tool, also ensure:
--helpis stable and in English
More from tumf/skills
firecrawl
|
60opencode-agent-creator
Create specialized OpenCode agents with proper configuration for primary agents and subagents. Use when the user wants reusable OpenCode agent profiles, needs `agent/*.md` files or `opencode.jsonc` agent entries, wants to configure prompts/models/tool access, or needs to split work between a primary agent and subagents safely.
49openclaw-agent-creator
|
26agentic-cli-design
|
22opencode-command-creator
Create custom OpenCode commands with proper structure, trigger descriptions, arguments, and configuration. Use when the user wants reusable slash/command workflows in OpenCode, needs `.opencode/commands/*.md` or `opencode.jsonc` entries, wants command templates with `$ARGUMENTS`, or needs to override/extend built-in commands safely.
21product-improvement-proposal
Propose concrete, high-leverage product/UX improvements to increase a software project's appeal and retention. Use when asked to generate product improvement proposals, UX ideas, onboarding/doc improvements, packaging/pricing positioning suggestions grounded in repo evidence, and prioritized MVP plans (ideation only; no implementation).
18