Menu
SkillsMP has collected 14 skills from Orkas-AI/Orkas-Awesome-AgentSkills. Open a skill to review its source and details.
Showing 14 of 14 collected skills.
Capture, organize, search, and synthesize knowledge inside a Notion workspace. Use this skill whenever the user wants to save content to Notion, update a Notion knowledge base, or research a topic from internal Notion pages.
Work with Obsidian vaults and Web Clipper templates. Use this skill whenever the user asks to search, create, edit, move, rename, or delete Obsidian notes, maintain wikilinks, inspect vault paths, or generate an Obsidian Web Clipper JSON template.
Fetch public social posts and analyze social/campaign metrics. Use this skill whenever the user asks to collect public social discussion, analyze social sentiment inputs, calculate engagement/CTR/ROI, compare platforms/content, or turn social samples into…
Plan e-commerce merchandise creatives: visual copy, product image prompts, product video prompts, ad scripts, storyboards, CTAs, compliance gates, and creative tests.
Source text: Chinese
Write and optimize e-commerce merchandise listing pages, titles, bullets, descriptions, SEO keywords, FAQs, Amazon A+ content, and competitor page diagnostics.
Source text: Chinese
Research e-commerce merchandise opportunities, category viability, price bands, competitors, profit assumptions, sourcing risks, and evidence gaps across Amazon and Chinese commerce platforms.
Source text: Chinese
Analyze e-commerce product reviews, ratings, and competitor feedback with privacy handling, VOC taxonomy, root-cause classification, evidence snippets, and prioritized improvement actions.
Source text: Chinese
Use for product requirement analysis before PRD writing: validate product or startup ideas, synthesize user research, compare competitors, score opportunity strength, surface hidden assumptions, and decide the next validation step. Use when the user asks…
Use for product development work from PRD to implementation: make technical decisions, stress-test plans, document ADRs or spike/POC findings, break down engineering work, plan files/modules, implement code changes, use TDD when practical, debug issues,…
Source text: Chinese
Use to write or refine a PRD after product demand is reasonably understood and before acceptance criteria, design handoff, engineering breakdown, or implementation planning. Use when the user asks for a PRD, product requirements document, scope definition,…
Use after a product direction, feature, MVP, release, or experiment exists and the user needs measurement or evidence-based review: plan analytics instrumentation before launch, create data QA checks, review post-release metrics and feedback, and recommend…
Use to turn a PRD section, user story, feature slice, or behavior description into product test scenarios and pass/fail conditions. Use when the user asks for product testing, acceptance criteria, Given/When/Then scenarios, QA-ready scenarios, pass/fail…
Use to design and implement product UI from PRD, product goals, user flows, or existing app context. Use when the user asks to build or improve a UI, frontend screen, landing page, dashboard, component set, design-system-based interface, Figma-style brief…
Use for SwiftUI development work: review and refactor SwiftUI view structure, Observation usage, MV patterns, dependency boundaries, and ViewModel choices; audit SwiftUI rendering, state updates, scrolling, layout, and Instruments evidence; or use…