Skip to main content

tedivm/opencode-config

SkillsMP has collected 16 skills from tedivm/opencode-config. Open a skill to review its source and details.

Latest recorded source activity
SkillsMP catalog refreshed
skills collected
16
GitHub stars
13
GitHub forks
1

Showing 16 of 16 collected skills.

occupation
Computer Occupations, All Other
description

Use when creating, configuring, or modifying opencode agents. Covers Markdown agent definitions, frontmatter options (description, mode, hidden, color), primary vs subagent types, and detailed prompt structure. Don't use for skills, commands, or general…

updated
occupation
Software Developers
description

Use when rendering mermaid diagrams to PNG, SVG, or PDF images. Handles both .mmd files and inline mermaid code blocks in markdown files. Don't use for creating mermaid syntax or GraphViz/DOT diagrams.

updated
occupation
Office Clerks, General
description

Use when converting files to Markdown format for LLM consumption, document analysis, or text extraction. Supports PDF, Office documents, images, audio, HTML, and more via Microsoft's markitdown. Don't use for simple text file reads, existing Markdown files,…

updated
occupation
Software Developers
description

Use when creating or modifying custom opencode commands in the `commands/` directory. Covers markdown command files, frontmatter options (description, agent, model, subtask), prompt templates with $ARGUMENTS, shell output injection, and file references.

updated
occupation
Software Developers
description

Use to do a thorough exploration of an existing codebase. Always use this when asked to explore a codebase/repo/project. Always use it when starting a task that requires deep knowledge of the codebase. Don't use for quick lookups or single-file questions.

updated
occupation
Software Developers
description

You MUST use when creating, modifying, or reviewing GitHub Actions workflow files. For security reasons it is VITAL that you use this skill when working with third party actions (including `actions/checkout` and other official actions).

updated
occupation
Software Developers
description

Use when parsing, querying, transforming, or extracting data from JSON files, API responses, or JSON streams. Always use the `jq` CLI for all JSON operations. Do not use for YAML, XML, CSV, or plain-text parsing. Never build JSON from scratch in Python, Node,…

updated
occupation
Software Developers
description

Use when designing software architecture or new features: producing technical design documents with model definitions, service code, API contracts, migration strategies, and testing plans. Works alongside OpenSpec proposals or stands alone for feature design.…

updated
occupation
Web & Digital Interface Designers
description

Use when implementing, extending, or adapting Rob's Style Guide design system in any framework (vanilla HTML, Svelte, React, etc.). Covers theming, colors, typography, components, Prism.js syntax highlighting, and Tabler Icons. Don't use for generic styling,…

updated
occupation
Computer Systems Analysts
description

Use when bootstrapping the design of a brand new project — producing a plan.md through iterative exploration. Don't use for modifying existing plans, implementing features, or working with established codebases.

updated
occupation
Network & Computer Systems Administrators
description

Use when creating a new Python project from Rob's Awesome Python Template (cookiecutter). Don't use for adding Python to existing projects, installing packages, or working with established codebases.

updated
occupation
Software Developers
description

Use when asked to create, generate, or scaffold a new Agent Skill. Don't use for modifying existing skills or writing general documentation.

updated
occupation
Software Developers
description

All actions on GitHub must use this skill. Covers pull requests, issues, repositories, releases, GitHub Actions, searches, and API requests via the `gh` CLI.

updated
occupation
Computer Systems Analysts
description

Use when initializing or setting up OpenSpec in a project that doesn't have it yet. Don't use for creating, applying, exploring, or tinkering with OpenSpec proposals.

updated
occupation
Software Developers
description

Use when creating a pull request, preparing changes for review, or pushing work to GitHub. Handles quality checks, branch management, conventional commits, openspec archival, and PR creation end-to-end.

updated
occupation
Software Quality Assurance Analysts & Testers
description

Use when asked to "fix things", "qa", "run tests and fix things", "test until clean", or similar requests to iteratively run quality checks and fix failures until everything passes. Don't use for single-purpose tasks like running only tests or only linting…

updated
Showing 16 of 16 collected skills.