Sylla-BV
@Sylla-BV Organization
Public Skills
coding-standards
by Sylla-BV
This skill should be used when the user asks about "Python coding standards", "Python code style", "type hints", "type annotations", "Optional vs union", "T None", "mypy", "black", "isort", "flake8", "ruff", "Pydantic models", "ConfigDict", "async patterns", "asyncio", "structlog", "error handling in Python", "Python naming conventions", "snake_case", "reviewing a Python PR", "does this pass Python code review", "BaseHarvester", "Dramatiq actors", "pydantic-settings", "pytest conventions", or wants to know whether code follows Sylla's Python data-engine repository standards.
verify
by Sylla-BV
This skill should be used when the user says "verify", "check my work", "review Python code", "check code quality", "run a code review", "review this PR", "check for code smells", "review against SOLID", "check DRY violations", "review Python files", "quality check", "is this clean code", "review my changes", "run checks", "validate", or wants a structured code quality review of Python files against SOLID, DRY, KISS, YAGNI, clean code, error handling, security, and performance principles.
code-upkeep
by Sylla-BV
This skill should be used when the user asks to "update docstrings", "audit docstrings", "fix docstrings", "add docstrings", "check docstrings", "Google-style docstrings", "add field descriptions", "update tests", "audit test coverage", "generate tests", "add tests", "fix tests", "write pytest tests", "check test coverage", "missing tests", "stale tests", "test this module", "add test cases", "bring code up to date", "code upkeep", "maintain code", or wants to audit and update Python docstrings or tests.
ticket-creator
by Sylla-BV
This skill should be used when the user asks to "create a ticket", "create a Linear ticket", "make a ticket", "write a ticket", "create an issue", "file a bug", "create a feature ticket", "write a bug report", "I need a ticket for...", "there's a bug in...", "turn this into a ticket", "write this up as a ticket", or wants to create any Linear issue for implementation.
coding-standards
by Sylla-BV
This skill should be used when the user asks about "coding standards", "code style", "how should I write this", "is this correct style", "what's the convention for", "interface vs type", "should I use React.FC", "how do we handle errors", "tryCatch pattern", "db query style", "arrow functions", "named vs default export", "how to structure this file", "barrel files", "institutionId", "multi-tenant", "page-content pattern", "naming conventions", "SCREAMING_SNAKE_CASE", "reviewing a PR", "does this pass code review", or wants to know whether code follows Sylla's Next.js 16 repository standards.
agent-browser
by Sylla-BV
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
verify
by Sylla-BV
This skill should be used when the user says "verify", "check my work", "am I done", "run checks", or "validate". Also use when implementation is complete, a plan has been executed, a mid-to-large feature is finished, or the user is about to open a PR or run superpowers:finishing-a-development-branch.