OpenParable
Skip to content

Find the skill for your next task.

Browse reusable Agent Skills, each with a clear purpose and practical guidance.

reviewing-readability

Evaluates comments, docstrings, and naming in code for readability by a developer new to the codebase — is the documentation clear and concise, and is non-obvious logic documented? Produces findings with concrete proposed rewrites (or additions where documentation is missing); the caller decides whether to apply them or present them as feedback. Use when reviewing a PR, branch, or set of changes for comment quality, naming clarity, or documentation readability. For a PR's title and description, use reviewing-pr-description instead.

45.24k repo stars4.32k repo forks
Testing & Quality

sharing-pr-agent-artifacts

Uploads agent-generated artifacts (specs, plans, learnings) to the streamlit.wiki for sharing via PR comments. Use when you have agent artifacts to share with reviewers.

45.24k repo stars4.32k repo forks
Productivity

understanding-streamlit-architecture

Explains Streamlit's internal architecture including backend runtime, frontend rendering, and WebSocket communication. Use when debugging cross-layer issues, understanding how features work end-to-end, planning architectural changes, or onboarding to the codebase. Covers ForwardMsg/BackMsg protocol, script rerun model, element tree, widget state management, and more.

45.24k repo stars4.32k repo forks
Testing & Quality

updating-internal-docs

Review internal documentation (*.md files) against the current codebase state and propose updates for outdated or incorrect information.

45.24k repo stars4.32k repo forks
Documents

writing-spec

Writes product and tech specs for new Streamlit features. Use when designing new API commands, widgets, or significant changes that need team review before implementation.

45.24k repo stars4.32k repo forks
Business

changelog

Use for writing, reviewing, editing, or generating Meteor release changelog entries. Defines canonical file locations, naming rules, required section structure, formatting conventions, PR-based generation workflow (with gh CLI and web fallback), incremental updates, and common entry patterns. Applies to files under v3-docs/docs/generators/changelog/versions/.

44.80k repo stars5.24k repo forks
Business

codebase

Use when understanding the build system, modifying CLI commands, working with isobuild, or navigating the tools/ directory. Covers build pipeline flow and file locations.

44.80k repo stars5.24k repo forks
Development

conventions

Use when writing new packages, adding CLI commands, creating build plugins, or following Meteor code patterns. Covers package.js structure, file naming, and common code patterns.

44.80k repo stars5.24k repo forks
Development

docs-gap

Use when analyzing release branch changes for missing user-facing documentation. Compares the release branch against devel, filters for user-facing changes, scans v3-docs/docs/ for coverage, and produces a gap report (.md file) with prioritized documentation opportunities. Does NOT write documentation — only identifies gaps and outputs a plan for later action.

44.80k repo stars5.24k repo forks
Productivity

e2e-coverage

Use when adding, modifying, or reviewing E2E test apps/skeletons to keep the test coverage report up to date.

44.80k repo stars5.24k repo forks
Testing & Quality