392 件 ・ 関連度順
概要と使いどころ
Use when evaluating stocks through Qiu Guolu's value-quality lens: stay within circle of competence, focus on industry leaders with structural advantages, and demand simple clear thesis before investing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating stocks through Deng Xiaofeng's cycle-and-industry lens: deep industry research, cycle position awareness, supply-demand dynamics, and buying leaders at cycle bottoms.
日本語の概要は準備中です。原文の説明を表示しています。
On-demand RAI planner reference pack covering Phase 1 capture, Phase 2 risk classification and the optional Mural board bootstrap, Phase 5 impact assessment, and Phase 6 review and backlog handoff.
日本語の概要は準備中です。原文の説明を表示しています。
Design data-driven Godot 4.7 games with custom Resource classes: define typed data with class_name + @export, save/load .tres/.res files, instance and duplicate resources, and load on demand with ResourceLoader (incl. threaded loading). Use when modeling items/stats/configs as data in a Godot project, creating .tres resources, or working with custom Resource subclasses and ResourceLoader/ResourceSaver.
日本語の概要は準備中です。原文の説明を表示しています。
Handle a dispute with a contractor — unfinished work, poor quality, overcharging, or a no-show — with a path that protects your money and your options. Use when asked to deal with a contractor dispute, my contractor did bad work / won't finish / overcharged, or how to get a builder to fix their work. Produces a read on your position (contract, payments, evidence), a firm-but-professional communication and demand path, documentation and payment-leverage guidance, and escalation options (mediation, licensing board, chargeback, small claims) — flagging that it's not legal advice.
日本語の概要は準備中です。原文の説明を表示しています。
Write a firm, effective complaint letter that gets a resolution. Use when asked to write a complaint letter, complain to a company about a product/service, escalate poor service, or demand a refund/replacement. Produces a structured complaint — the facts, the impact, the specific resolution you want, and a deadline — in a firm, professional tone that's hard to ignore and easy to act on.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a session's context window like the budget it is — what loads up front, what gets linked instead, what stays fetch-on-demand, and how to keep the stable prefix cache-friendly so repeated turns cost cents instead of dollars. Use when asked my agent keeps blowing its context, plan what to load into the session, why is every turn so expensive, or design the context for this workflow. Produces the load/link/fetch allocation, the cache-aware prefix layout, the per-turn cost shape, and the eviction rules for when the window fills anyway.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a firm, professional cease-and-desist letter to stop harassment, defamation, IP misuse, or unwanted contact — clear about what must stop and what happens if it doesn't. Use when asked to write a cease and desist, make someone stop [harassing/using my work/defaming me], or send a formal letter to stop. Produces a structured letter stating the conduct, why it's wrongful, the specific demand and deadline, and the consequence, plus guidance on delivery and records — flagging when the matter needs a real lawyer. Not legal advice.
日本語の概要は準備中です。原文の説明を表示しています。
Help users distinguish between deceptive tarpit ideas and high-potential opportunities by applying rigorous frameworks for market timing, business math, and user demand.
日本語の概要は準備中です。原文の説明を表示しています。
Read Printful products and orders, create orders and mockups. Trigger phrases: printful, print on demand, mockup, fulfillment, store orders.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the headline result of an American Economic Journal: Macroeconomics (AEJ: Macro) manuscript must be shown stable across specification, sample, identification, and tuning choices. Builds the robustness program a macro referee will demand; it does not establish the primary identification or model (use aejmac-identification / aejmac-theory-model first).
日本語の概要は準備中です。原文の説明を表示しています。
Use when judging whether a research idea fits Administrative Science Quarterly (ASQ) and has the *surprising* theoretical insight ASQ demands. Sharpens the puzzle and the contribution claim; it does not design the study or write theory sections.
日本語の概要は準備中です。原文の説明を表示しています。
Use when choosing or sharpening a research question for an Accounting, Organizations and Society (AOS) manuscript — testing whether the question genuinely concerns the social, organizational, behavioral or institutional life of accounting, and picking the intellectual tradition the question demands. Screens fit; it does not build the theory (aos-theory-development).
日本語の概要は準備中です。原文の説明を表示しています。
Discover rising category conversations, formats, sounds, questions, and creator patterns across social platforms, then separate durable demand signals from short-lived noise.
日本語の概要は準備中です。原文の説明を表示しています。
Turn TikTok, Instagram, YouTube, Facebook, X, LinkedIn, Reddit, or Rumble transcripts into timestamped hooks, claims, objections, proof, calls to action, sponsorship signals, and reusable content atoms. Use directly for transcript analysis or as support for creator, competitor, trend, demand, and repurposing work.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes alternative splicing from PacBio Iso-Seq (HiFi, Kinnex/MAS-Iso-seq) and Oxford Nanopore (direct cDNA, direct RNA, R10.4.1+) long-read RNA-seq with full-isoform resolution. Tools include FLAIR (correct/collapse/quantify/diffSplice for PacBio + ONT), IsoQuant (de-novo or annotation-guided isoform discovery 2024 SOTA), Bambu (annotation-aware Bayesian discovery + quantification with Novel Discovery Rate), SQANTI3 (isoform classification: FSM/ISM/NIC/NNC + artifact flags), rMATS-long (event calling on long-read isoforms), and minimap2 (-ax splice:hq for HiFi; -ax splice -k14 for ONT cDNA; add -uf only for direct RNA or stranded cDNA preps). Solves microexon detection, recursive splicing, complex multi-exon isoforms, and DTU without transcript-quantification uncertainty. Use when short-read AS limitations (anchor length, complex isoforms, microexons, recursive splicing, transcript ambiguity) demand full-isoform resolution.
日本語の概要は準備中です。原文の説明を表示しています。
Assesses RNA-seq data quality specifically for alternative splicing analysis. QC layers include experimental design audit (library prep, read length, depth, replicates), STAR 2-pass cohort-style alignment, junction saturation curves and discovery plateau detection, novel-vs-known junction ratio diagnostics, junction-overhang distribution, splice-site strength scoring (MaxEntScan intrinsic + SpliceAI context-aware), strandedness verification, GENCODE basic vs comprehensive choice, and rRNA contamination screening. Splicing analysis is more demanding than DGE on read length, depth, library prep, alignment strategy, and annotation choice — failures silently bias PSI estimates and inflate novel-junction false positives. Use when evaluating data suitability for splicing analysis, troubleshooting low event detection, or designing sequencing experiments where AS is a primary endpoint.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "write a test", "review these tests", "audit tests", "prune low-value tests", or "find duplicate tests", and whenever writing, changing, reviewing, or sweeping tests. Gates new tests and audits low-value, implementation-coupled, or duplicative tests and the test-only production seams they demand.
日本語の概要は準備中です。原文の説明を表示しています。
AWS EC2 virtual machine management — instances, security groups, key pairs, AMIs, EBS volumes, Auto Scaling Groups, Spot Instances, Session Manager, placement groups, and instance lifecycle automation. Trigger on ANY of these, even when EC2 isn't named explicitly: - Launching or provisioning: "spin up a server", "create a VM", "new instance", "run-instances", mention of instance types (t3, m5, c5, r6, g5, p4d, t4g, c7g, etc.) - SSH / connectivity problems: "connection refused", "connection timed out", "permission denied publickey", "can't connect to my instance", "SSH not working" - Instance management: resize, stop, start, terminate, reboot, change instance type - Cost optimization: stop dev instances overnight, save money on EC2, spot vs on-demand, reserved instances - Auto Scaling: ASG, launch template, mixed instances policy, scale to zero, scheduled scaling - Spot Instances: spot fleet, spot interruption, capacity-optimized, price-capacity-optimized - AMIs and backups: create image, custom AMI, EBS snapshot, DLM lifecycle policy, copy AMI - Monitoring: EC2 CPU utilization, CloudWatch metrics for instance, instance status checks, console output - Access methods: Session Manager, EC2 Instance Connect, bastion host, port forwarding - Security: IMDSv2, instance metadata, IAM role on instance, security group rules - User data and bootstrap scripts, cloud-init
日本語の概要は準備中です。原文の説明を表示しています。
Product research for TikTok Shop — viral potential scoring, creator demand, category analysis
日本語の概要は準備中です。原文の説明を表示しています。
Multi-location inventory — transfers, low stock alerts, demand forecasting, safety stock, ABC analysis
日本語の概要は準備中です。原文の説明を表示しています。
Inventory management for TikTok Shop — demand forecasting, viral stock planning, FBT optimization
日本語の概要は準備中です。原文の説明を表示しています。
POD integration — Printful, Printify, mockups, niche selection, margin optimization
日本語の概要は準備中です。原文の説明を表示しています。
Design a controlled dynamic-pricing or repricing system for ecommerce products. Use when a seller asks for demand-based, inventory-based, competitor-responsive, or time-based price rules; SKU eligibility; price floors and ceilings; automation approvals; simulations; monitoring; or rollback plans across Amazon, Shopify, TikTok Shop, Walmart, eBay, or other channels. Do not use for a one-time optimal-price calculation or to change live prices without explicit authorization.
日本語の概要は準備中です。原文の説明を表示しています。