property-based-testing
Automated guidance for implementing property-based testing (PBT) in software and smart contracts to improve test coverage and edge case detection.
Discover reusable agent skills, browse implementation details, and find the right skill for your workflow.
290 skills found
Automated guidance for implementing property-based testing (PBT) in software and smart contracts to improve test coverage and edge case detection.
Refactor monolithic notes into modular, index-linked files for improved discoverability and organization, targeting files over 1000 lines.
Automatically detect code changes and suggest documentation updates. Keeps READMEs, API specs, and configuration guides in sync with your implementation.
Connect to the Notion API to create, manage, and query pages, databases, and blocks for your AI-powered knowledge management.
A structured personal operating system for managing digital presence, knowledge, relationships, and goals with AI assistance for founders, creators, and professionals.
Provides targeted, concise English language editing and stylistic improvements for text without performing full rewrites.
Analyze business contracts for risks, gaps, and unfavorable terms. Generate structured risk reports for NDAs, MSAs, SaaS agreements, and SOWs with actionable redline recommendations.
Generate professional patent-style technical diagrams including flowcharts, system architectures, and block diagrams using Graphviz with automatic reference numbering.
Analyze, validate, and generate Schema.org structured data (JSON-LD). Detect markup, identify opportunities, and ensure compliance with Google's rich result guidelines.
Build AI agents with the OpenAI Agents SDK for Python. Supports multi-agent handoffs, function tools, stateful sessions, streaming, and Azure OpenAI integration via LiteLLM.
Upstash Vector DB setup, semantic search, namespaces, and embedding models. Ideal for building high-performance vector search features in Next.js 16/Vercel projects.
Identify and document Customer Problems (CP) from business context. Use when starting requirements engineering or when stakeholders describe solutions instead of problems. Step 1 of Problem-Based SRS methodology.