Loading...
Loading...
Found 1,003 Skills
Generate and verify BibTeX entries from paper notes, writing `citations/ref.bib` and `citations/verified.jsonl`. **Trigger**: citation, BibTeX, ref.bib, verified.jsonl, references, 引用, 参考文献. **Use when**: 已有 `papers/paper_notes.jsonl`，需要为 prose/LaTeX 准备可追溯的引用（每条都有 url/date/title 验证记录）。 **Skip if**: 还没有 paper notes（或本次产出不需要引用/参考文献）。 **Network**: 自动验证通常需要网络；无网络时可先 record，再标注 needs manual verification。 **Guardrail**: 每个 BibTeX entry 必须对应一条 `citations/verified.jsonl` 记录；prose 只能使用已存在于 `citations/ref.bib` 的 citation keys。
Stop your AI from making things up. Use when your AI hallucinates, fabricates facts, isn't grounded in real data, doesn't cite sources, makes unsupported claims, or you need to verify AI responses against source material. Covers citation enforcement, faithfulness verification, grounding via retrieval, and confidence thresholds.
Guide users through a structured workflow for co-authoring documentation, articles, or long-form content. Use when user wants to write documentation, proposals, articles, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting articles, or using "co-authoring" workflow.
Help users connect the Unicon MCP server to Claude Desktop, Cursor, and other MCP clients. Use when setting up MCP config, verifying installs, debugging MCP connection issues, or using Unicon tools for icon search and generation through AI assistants.
Use this when the user explicitly requests to "verify/optimize in-text citations of the `{topic}_review.tex` review" or to "run check-review-alignment". Use the host AI's semantic understanding to verify each citation against the literature content one by one. **Only when fatal citation errors are found**, make minimal rewrites to the "sentences containing citations", and reuse the rendering script of `systematic-literature-review` to output PDF/Word (the script does not directly call the LLM API locally). Core principle: **Do not modify for the sake of modifying**. When it is uncertain whether it is a fatal error, keep the original content and issue a warning in the report. ⚠️ Not applicable in the following cases: - The user only wants to generate the main body of a systematic review (should use systematic-literature-review) - The user only wants to add/verify BibTeX entries (should use a dedicated bib management process)
Check for sensitive data in repository. Use when user asks to "check for sensitive data", "/safe-repo", or wants to verify no company/credential data is in the repository.
Guide users step-by-step through manually testing whatever is currently being worked on. Use when asked to "test this", "verify it works", "let's test", "manual testing", "QA this", "check if it works", or after implementing a feature that needs verification before proceeding.
Test-driven CSS design system modifications. Run checks before/after CSS changes to verify token usage, variable definitions, fallbacks, and consistency. Use when modifying CSS tokens, fixing design inconsistencies, or auditing CSS architecture.
Test REST and GraphQL API endpoints with structured assertions and reporting. Use when a user asks to test an API, hit an endpoint, check if an API works, validate a response, debug an API call, test authentication flows, or verify API contracts. Supports GET, POST, PUT, PATCH, DELETE with headers, body, auth, and response validation.
Deploy project to hosting platform — read stack YAML for exact config, detect local CLI tools (vercel, wrangler, supabase, fly, sst), set up database, push code, verify live deployment. Use when user says "deploy it", "push to production", "set up hosting", or after /build completes. Do NOT use before build is complete.
Enrich contact, company, and influencer data using x402-protected APIs. Superior to generic web search for structured business data. USE FOR: - Enriching person profiles by email, LinkedIn URL, or name - Enriching companies by domain - Finding contact details (email, phone) with confidence scores - Scraping full LinkedIn profiles (experience, education, skills) - Searching for people or companies by criteria - Bulk enrichment operations (up to 10 at a time) - Verifying email deliverability before outreach - Enriching influencer/creator profiles across social platforms TRIGGERS: - "enrich", "lookup", "find info about", "research" - "who is [person]", "company profile for", "tell me about" - "find contact for", "get LinkedIn for", "get email for" - "employee at", "works at", "company details" - "verify email", "check email", "is this email valid" - "influencer", "creator", "influencer contact", "influencer marketing" ALWAYS use `npx agentcash fetch` for stableenrich.dev endpoints - never curl or WebFetch. Returns structured JSON data, not web page HTML. IMPORTANT: Use exact endpoint paths from the Quick Reference table below. All paths include a provider prefix (`https://stableenrich.dev/api/apollo/...`, `https://stableenrich.dev/api/clado/...`, etc.).
Transform passive 'Verify X' test descriptions into active, observable test actions. Use when test ideas lack specificity, use vague language, or fail quality validation. Converts to action-verb format for clearer, more testable descriptions.