Loading...
Loading...
Found 9,402 Skills
Collect profile pages from Threads — username, bio, followers, posts count, website. Use when the user wants to research creators, find influencers, or build lead lists.
Collect job and company leads from Seek — company name, job title, location, posting date, company website. Use when the user wants to find hiring companies in Australia and New Zealand.
Collect reviews from Naver Shopping — text, rating, author, date, verified status. Use when the user wants to collect reviews for sentiment analysis or quality research.
Collect shops from Etsy — shop name, rating, reviews, product catalog. Use when the user wants to research shops or find niche sellers.
Collect contact details from website contact pages — email, phone, address, contact form URL, social profiles. Use when the user wants to extract contact information from a company's website.
Collect comments from TikTok — text, author, timestamp, likes, replies. Use when the user wants to mine audience feedback, questions, or sentiment.
Collect Amazon product details by ASIN from Amazon — ASIN, title, price, rank, reviews, variants. Use when the user wants to look up product data directly by ASIN.
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule from an accepted design correction.
Watch any video (URL, stream, or local path) via Watch Skill. Downloads, extracts scene-aware deduped frames, OCRs them, transcribes (captions first, then local Whisper — offline by default), indexes everything, and hands the result to the agent. Follow-up questions are answered from the persistent index without re-processing.
Use this skill when adding and configuring the RevenueCat Android SDK (purchases-kt/purchases) in an app. Covers the Gradle dependency, Purchases.configure with PurchasesConfiguration, initial app user id strategy, and log level.
Investigate a GitHub issue — fan out parallel exploration, find the root cause (5 Whys, evidence-backed), and write a reviewable RCA artifact (then post a summary to the issue). The investigate step before piv-implement-issue. Use to diagnose a bug/issue before fixing it.
Push the current feature branch and open a pull request, ready for review. Use after a ticket's implementation is committed on its own branch — it detects the base branch, pushes, opens the PR with a clear body (summary · what changed · validation status), and returns the URL to hand to a reviewer.