829 件 ・ 関連度順
概要と使いどころ
Create and format WeChat Official Account (公众号) articles with proper Markdown-to-WeChat HTML conversion, rich formatting, cover image guidance, and both API and manual publishing workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Matches a user’s biomedical research direction, disease problem, study aim, data modality, and resource constraints to the most relevant recent algorithms and method papers. Always search real recent algorithm literature first, prioritize the last 12 months, expand to 1–3 years only when needed, and add canonical baselines only when necessary. Every formal algorithm recommendation must include the verified primary method paper, plus published downstream papers that actually cite/use the algorithm when such papers are found, with DOI when available. Never fabricate papers, algorithm names, authors, journals, years, DOI, PMID, links, or benchmark claims. If no directly verified algorithm paper is found, say so explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
Tracks the latest preprints and emerging research topics related to your topic across bioRxiv, medRxiv, and arXiv. Use when a user wants to discover what is being published right now before it reaches journals, monitor competitor directions, spot new methodology trends, or get an early-warning scan of a research area. Triggers on phrases like "what's new in X", "latest preprints on Y", "emerging topics in Z", "monitor bioRxiv for", or "what are people working on in this field".
日本語の概要は準備中です。原文の説明を表示しています。
Create distributable Python packages with proper project structure, setup.py/pyproject.toml, and publishing to PyPI. Use when packaging Python libraries, creating CLI tools, or distributing Python code.
日本語の概要は準備中です。原文の説明を表示しています。
Smallest personal narrated-explainer-video pipeline (spoken narration over visuals, not an audio podcast), fully tool-agnostic and autonomous by default — topic → research ∥ asset collection → script → TTS → video → 4K render ∥ publish info + cover. The skill defines the pipeline logic and self-verified checkpoints; any TTS backend and any video tool (Remotion, HyperFrames, CapCut, ...) work, and how much human oversight to apply is set by the working project's AGENTS.md/CLAUDE.md, not here. Use when the user wants a quick personal narrated video with minimal steps, whether or not they name the tool stack. Do NOT trigger for audio-only podcasts, written episodic content, or heavy multi-format production.
日本語の概要は準備中です。原文の説明を表示しています。
Minimal personal narrated-video pipeline — a topic becomes a talking-head-free explainer MP4 (1080p or 4K) via script → Azure TTS (SSML) → Remotion. Use when the user wants a quick narrated video from a topic without the full video-podcast-maker machinery (no extra skills, no thumbnails/shorts/publish matrix). Do NOT trigger for heavy production needs — use video-podcast-maker for those.
日本語の概要は準備中です。原文の説明を表示しています。
Episode and season structure for TV series (剧集单集与季的结构) — teasers and cold opens, broadcast four/five/six-act grids with page anchors, three tests for finding the invisible acts in streaming scripts, act-out and cliffhanger taxonomies, Oberg's four information tools, A/B/C/runner weaving and scene-count ratios, the Calvisi pilot beat sheet, five-part scene structure, and season shape (tentpoles, bottle and container episodes, two-parters, finales). Merged from Calvisi, Douglas, Oberg, Landau, Goldberg & Rabkin, Miller, Rabkin and Blum, plus act lengths measured from published West Wing, Succession, Sopranos, Downton and Fleabag scripts. Use when breaking an episode into acts, deciding how many acts a script needs, placing act outs and cliffhangers, designing a teaser, weaving A/B/C stories and runners, beating out a one-hour pilot, auditing an episode that has no shape, reverse-engineering a show's structure, or planning a season's episode order (分幕、出幕、悬念结局、季弧、瓶子集).
日本語の概要は準備中です。原文の説明を表示しています。
Produce a CV shaped for one target company and role: its applicant tracking system, the country's conventions, the sector's norms, its published values and the job ad, with every choice explained. Use when asked to write my CV for a specific company, tailor my CV to Google, Amazon or any named employer, make my CV fit this company's format, or turn my experience into a CV for this job. Produces the tailored CV, a short format rationale citing public sources with dates, and a list of claims the person must be ready to defend. Never invents experience or insider knowledge.
日本語の概要は準備中です。原文の説明を表示しています。
Sanity-check a greenhouse gas inventory before it goes into a report or gets audited. Use when asked to review a carbon footprint, check a GHG inventory, validate scope 1/2/3 numbers, explain a year-over-year emissions change, or prepare emissions data for assurance. Produces a boundary review, data-quality assessment, emission-factor sensitivity list, YoY bridge, and a fix-before-publishing list.
日本語の概要は準備中です。原文の説明を表示しています。
Publish 'how to work with me' as a literal API spec — endpoints (what to ask me for and what you'll get back), rate limits (meeting and interrupt tolerance), error codes (what happens when you surprise me Friday 5pm), auth (how to earn trust), and a changelog. Use when onboarding to a new team, when a new manager or report arrives, for a team working-styles session, or 'write my README/user manual'. Produces a personal API spec that's genuinely funny and secretly the best onboarding doc on the team.
日本語の概要は準備中です。原文の説明を表示しています。
Write and lint the title and thumbnail for a YouTube video as one pairing, checking truncation, duplication and vagueness before publish. Use for "title ideas", "what should I call this", "thumbnail text", "my CTR is bad", packaging, or any request to rename or repackage an existing video.
日本語の概要は準備中です。原文の説明を表示しています。
Verifies truthfulness, accuracy, and link integrity of content before publishing. Catches fabricated statistics, dead URLs, misattributed sources, and company claims that contradict the brand DNA.
日本語の概要は準備中です。原文の説明を表示しています。
Registry fallback entry point for the VidSeeds.ai MCP connector. Use the bundled domain skills for setup, efficiency, thumbnails, projects, analytics, local video, and publishing workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding WHERE to point SEO effort, not how to write a page. Triggers: a new site or brand with no rankings and no authority ("cold start", "starting from zero", "nobody knows us"), deciding what to double down on, a page or cluster that ranks but earns nothing, hunting emerging or newly-coined keywords before competitors arrive, "should we build a cluster or one page", "what do we write next", "we get impressions but no clicks", "our traffic plateaued despite publishing", whether to chase a head term at all, or turning any of it into recurring automation. Also use when asked why an SEO effort stalled despite consistent output. NOT for writing an article, keyword expansion mechanics, or auditing a single tactic for penalty risk.
日本語の概要は準備中です。原文の説明を表示しています。
Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email, domain/DNS). The human connects accounts and approves changes; supported wiring operations run through a local CLI and produce verification evidence with explicit limits. Use when the user wants to ship, deploy, go live, launch, publish, or put their app online, or asks to wire up env vars, webhooks, auth settings (signup, email confirmation, password policy), a real signup → confirmation email → login journey, password recovery, account isolation between two users, auth redirects, email DNS or a custom domain.
日本語の概要は準備中です。原文の説明を表示しています。
Review generated or changed documentation before it ships — READMEs, API references, docstrings, PHPDoc/JSDoc, changelogs, tutorials, and doc sites. Best used reactively after an agent writes or edits docs, after code changes documented behavior, or before publishing docs. Use when the user says 'review the docs', 'is this documentation accurate', 'update the docs', 'write a README', 'document this API', 'add a docstring', or 'add a changelog entry'. Core job: verify every referenced function, flag, endpoint, config key, and code sample against the source; catch docs-vs-code drift; strip filler and unverifiable claims. DO NOT USE for production code review (use clean-code-guard), test review (use test-guard), marketing copy or blog posts, prose style editing of non-technical writing, or documentation site theming.
日本語の概要は準備中です。原文の説明を表示しています。
Use when positioning the contribution of an American Economic Review: Insights (AER: Insights) short-format manuscript against the closest published work in one or two tight paragraphs. Stakes the gap concisely; it does not write the full literature review (there is no room for one).
日本語の概要は準備中です。原文の説明を表示しています。
Use when choosing and applying a theory-construction method for an Academy of Management Review (AMR) manuscript — building constructs, defining their domain, specifying relationships, articulating the underlying logic/mechanisms, and setting boundary conditions. This is the THEORY-CONSTRUCTION craft, NOT empirical method; AMR publishes no datasets, no measures, and no statistical tests.
日本語の概要は準備中です。原文の説明を表示しています。
Use when positioning an ACL submission against the NLP literature, covering ACL Anthology citation practice, arXiv-versus-published version citation, concurrent LLM-era preprints, prior-cycle ARR resubmission overlap, anonymity-preserving self-citation, and the fast-moving baseline problem in computational linguistics.
日本語の概要は準備中です。原文の説明を表示しています。
Use when stress-testing the LOGIC of an Academy of Management Review (AMR) theory manuscript — checking logical coherence, running thought experiments and counterfactuals, addressing alternative explanations and disconfirming cases, and verifying each proposition follows from its argument. This is ARGUMENT DEVELOPMENT, NOT data analysis; AMR publishes no datasets, no statistics, and no empirical results.
日本語の概要は準備中です。原文の説明を表示しています。
Mandatory pre-publish review gate for a UGC video render. Transcribes the finished render's AUDIO with Whisper and word-diffs it against the approved spoken script, then gates pinning the final render (video_project_upsert patch.final_render_id) — blocking a render whose generated audio mis-voices a word (e.g. the approved "human-vetted" spoken as "human witted"), says a different number or brand name, flips a negation, drops an approved phrase, or comes back silent. Correct speech written differently ("5mg" said "five milligrams", "30%" said "thirty percent", a spoken URL, "don't" said "do not", "braxleybands" said "braxley bands", a confirmed pronunciation like "AG1" said "A G one") passes. Runnable, gating counterpart to content-goose's review-transcript-integrity atom. Every ugc-video-formats recipe runs this after render and BEFORE pinning the final render.
日本語の概要は準備中です。原文の説明を表示しています。
Crawl a website's sitemap and blog index to build a complete content inventory. Lists every page with URL, title, publish date, content type, and topic cluster. Groups content by category and topic. Optionally deep-reads top N pages for quality analysis and funnel stage tagging. Use before SEO audits, content gap analysis, or brand voice extraction.
日本語の概要は準備中です。原文の説明を表示しています。
Creates a new graphics format spec (custom canvas dimensions + content rules) and publishes it to the Gooseworks library so any agent can render against it. Use when the existing community formats (carousel, story, infographic, slides, poster, chart, tweet, plus community additions) don't fit the user's canvas — e.g., LinkedIn banner 1584×396, story cover 1080×1920, event flyer 8.5×11in. Mirrors goose-graphics-create-style but for formats.
日本語の概要は準備中です。原文の説明を表示しています。
Monitor competitor content across blogs, LinkedIn, and Twitter/X on a recurring basis. Surfaces new posts, trending topics, and content gaps you can own. Chains blog-feed-monitor, linkedin-profile-post-scraper, and twitter-mention-tracker. Use when you want a weekly digest of what competitors are publishing and which topics are generating engagement.
日本語の概要は準備中です。原文の説明を表示しています。