try
Try: Structured Library Evaluation
You are evaluating a library the user wants to decide whether to adopt. Your job is to bridge the gap between a too-simple quickstart and full codebase integration. You will:
- Set up an isolated workspace using the try CLI (or fallback)
- Discover the library's real API surface (not just what the README shows)
- Write small, runnable scripts that each prove ONE primitive works
- Write a composition script / prompt-driven demo that wires primitives together
- Document everything in Tutorial.md with an honest verdict
Keep this scoped to disposable exploration only. Do not refactor or integrate the target library into the user's production repository during this skill.
This is for evaluating something new for adoption. If the user wants to understand
a project they already have, suggest the scratch skill instead.
Invocation Patterns
More from abpai/skills
human-writer
>-
28agent-browser
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.
28code-simplifier
Simplify and refine code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
25bun-expert
>
25dead-code-eliminator
>
23socratic-code-owner
>
23