opper-api
Direct access to the Opper REST API for LLM orchestration, model management, task execution, and seamless migration from OpenAI, Anthropic, or OpenRouter.
Discover reusable agent skills, browse implementation details, and find the right skill for your workflow.
322 skills found
Direct access to the Opper REST API for LLM orchestration, model management, task execution, and seamless migration from OpenAI, Anthropic, or OpenRouter.
Manually triggers a Hipocampus memory flush to persist current session context to raw logs and initiate the compaction tree process for long-term agent memory maintenance.
Analyze RFPs and requirements to identify stakeholders, decompose functional modules, extract constraints, and generate high-priority clarification questions.
Build systematic evaluation frameworks for AI agents using multi-dimensional rubrics, LLM-as-a-judge, and regression testing to measure performance, quality, and context engineering effectiveness.
Analyze meeting transcripts to uncover behavioral patterns, communication insights, and leadership feedback. Identify conflict avoidance, filler words, speaking ratios, and active listening to improve your professional presence.
Advanced web scraping using Firecrawl API for deep content extraction, page interaction, screenshots, and PDF parsing.
Implement a full Model Context Protocol (MCP) stack in Rails. Connect to external servers, expose your Rails app as an MCP server, or manage subprocess MCP containers via Docker with OAuth 2.1 PKCE support.
Enforce structured JSON output from Claude models using Bedrock tool_use to eliminate parsing failures and ensure schema compliance.
Automated CLI tool to scrape and convert Notion, DocSend, PDFs, and general web documents into local PDF files with session persistence and daemon support.
Connect to the Notion API to create, manage, and query pages, databases, and blocks for your AI-powered knowledge management.
Universal CLI tool to convert and synchronize AI agent skills between Claude Code and Gemini CLI extensions.
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.