Total 51,164 skills
Showing 12 of 51164 skills
Blockbench plugin/extension development for the 3D modeling tool. Use when creating, modifying, or debugging JavaScript plugins for Blockbench including actions, dialogs, panels, menus, toolbars, model manipulation, animation APIs, and custom formats/codecs. Triggers on Blockbench plugin, Blockbench extension, Blockbench API, BBPlugin, model editor plugin, or 3D modeling tool extension.
Turn a completed experiment iteration into an honest, evidence-backed analysis — a markdown report and a portable data dump. Pulls run data via the tpc CLI, scores each task, clusters friction by root cause (with a transcript example per claim), compares arms, and closes on agent-readiness gaps. The natural companion to setup-experiment: setup → run → analyze. Trigger when users say: "analyze my experiment", "write the report", "experiment report", "analyze the results", "summarize the runs", "what happened in this iteration", "friction report", or "report gen".
Scraper de Macrotrends: financial statements, ratios, employee count con 15+ años de data histórica. Sin API key.
Trading API de Primary (Matba ROFEX): futuros, opciones, acciones, bonos. Órdenes, posiciones, cuenta, market data.
Trading API de Alpaca: órdenes, posiciones, cuenta. Paper trading y live trading de acciones, crypto y opciones.
Build the optimal 250-byte Amazon backend search term string. Collects every candidate keyword, removes anything already indexed in the title and bullets, strips duplicates and Amazon-prohibited terms, prioritizes by search value, and packs the field to the byte limit. Use when a user asks about backend keywords, search terms, the hidden keyword field, generic keywords, "Search Terms" in the listing back end, or wants to fix wasted backend space. Trigger phrases: "backend keywords", "search terms field", "hidden keywords", "250 bytes", "generic keywords". Works with zero tools. the user pastes the current title, bullets, and any keyword list.
Build Amazon FBA reimbursement claims under the 2025 manufacturing-cost policy. Identifies eligible cases (lost units, warehouse-damaged units, customer-return losses, fee errors), assembles the cost-basis evidence Amazon now requires, and produces a claim packet per case within the 60-day window. Use when a user asks about FBA reimbursements, lost inventory claims, warehouse damage, the new reimbursement policy, manufacturing cost evidence, or unrecovered refunds. Trigger phrases: "reimbursement", "FBA claim", "lost inventory", "warehouse damage", "manufacturing cost", "60 day window", "SAFE-T". Works with zero tools. the user pastes the relevant Amazon report rows and supplier invoices.
Compare Amazon inbound shipment placement options (minimal-split vs Amazon- optimized split, partial-split, optional unified inventory) given SKU dimensions, units, and destination forecast. Returns the lowest landed cost per unit. Use when a user asks about STA (Send to Amazon), inbound placement fees, shipment splits, fulfillment center routing, or inbound shipping optimization. Trigger phrases: "STA", "inbound placement", "shipment split", "placement fee", "fulfillment center routing". Works with zero tools.
Optimize a full Amazon listing for both ranking and conversion, and diagnose why a listing is not ranking against the A9 + COSMO pillars. Rewrites the title, bullets, and description, places keywords correctly, sharpens the benefit argument, and checks policy and mobile compliance. Use when a user asks to optimize a listing, improve a title, rewrite bullets, fix a listing that does not convert, improve listing copy, do a listing makeover, rank higher in search, audit search visibility, or asks about the A9 or COSMO algorithm. Trigger phrases: "optimize my listing", "listing optimization", "rewrite my bullets", "improve my title", "listing not converting", "listing makeover", "amazon SEO", "rank higher", "A9", "COSMO", "search ranking", "search visibility", "why doesn't my listing rank". Works with zero tools.
Plan an Amazon Subscribe and Save strategy for consumable and replenishable products. Decides if a product fits, sets the discount tier, and builds a plan to convert one-time buyers into subscribers and keep them. Use when a user asks about Subscribe and Save, SnS, recurring revenue on Amazon, subscription discounts, converting buyers into subscribers, or retention. Trigger phrases: "subscribe and save", "SnS", "subscription", "recurring revenue", "repeat buyers", "retention", "replenishment". Works with zero tools.
Transmission Psychology Decoder. Given a piece of content, use 5 classic communication theories to decode why it resonates with the audience, analyze the underlying audience emotions and effective stance, and output discussion directions for chatrooms. Triggers: /dbs-spread, "Transmission Psychology Decoder", "Why did this go viral", "What do the audience want to hear", "What emotion does this content hit" Transmission psychology decoder. Given a piece of content, analyze the psychological mechanism that makes it resonate, identify the emotional core and effective stance, and output direction for chatroom discussion. Trigger: /dbs-spread, "why does this resonate", "what emotion does this hit", "decode this content"
Audit Lightning Web Components for SLDS compliance and produce a scored quality report. Runs the SLDS linter, analyzes CSS for theming hook usage and pairing, checks HTML for accessibility attributes, and scores findings across categories into an overall grade. Use when asked to "score my component", "SLDS scorecard", "quality report", "audit SLDS compliance", "how good is my SLDS", "check component quality", "rate my component", "evaluate my component", "is this component ready to ship?", "look at my LWC for issues", "audit this before I submit", "review my component before code review", or any time a user wants a quality assessment or production-readiness check on an LWC or SLDS component. Not for fixing violations (use design-systems-slds2-migrate) or building new components (use design-systems-slds-apply).