62 skills · sorted by relevance
Investigate a username, file, code identifier, URL, or concept by exploring connected entities across relevant sources. Produce a dossier with a summary, relationship diagram, source references, and a machine-readable JSON graph.
Build a structured research dossier for a defined patient population, covering epidemiology, disease biology, current treatment, regulatory precedents, and major clinical trials. Receive a cited report and structured data to inform therapeutic development and trial planning.
Structured intelligence dossiers on companies, people, markets, or domains, with source triangulation and fact/inference discipline. Use when preparing a deal-prep dossier, executive briefing, or due-diligence overview.
The English summary is being prepared. Showing the original description.
Front-door router voor het werken aan een regelrecht-dossier. Gebruik dit aan het begin van een dossier, of bij twijfel over waar te beginnen — het triageert de situatie en routeert naar de juiste skill (regelrecht-stelselanalyse voor desk-review/corpus-completion, regelrecht-audit-products voor live expert-validatie) en de juiste volgorde. Bevat het routeringsprincipe: feitelijke defecten routeren naar de desk, oordeels-/praktijkvragen naar de workshop. Dossier-agnostisch.
The English summary is being prepared. Showing the original description.
Build threat actor profiles from public reports, social media, code repositories, and other intelligence sources. Correlates indicators, maps related infrastructure and attack techniques, and produces structured dossiers with confidence assessments about who may be responsible.
Use when the user asks to "codify how our founder sounds", "build a founder voice dossier", or "set our content pillars"; runs an 80%-extraction interview over the user's OWN posts, emails, and decks (never competitor scraping, never an invented persona) and produces the versioned voice record — a per-platform register map (incl. 小红书/微信公众号), banned phrases, per-context disclosure lines (the ECHO C2 upstream), a few-shot bank built exclusively from own posts, and 3-5 content pillars with Estimated %-allocations — submitted via memory/events/channels.ndjson for channel-registry to store as voice-dossier.md, the record every Craft-phase skill reads first. Not for the brand-level voice canon — use brand-language-codifier; not for audience/persona research — use audience-mapper. 声音档案/品牌语气/创始人语气/内容支柱/披露声明
The English summary is being prepared. Showing the original description.
Use when the user asks to "codify how our founder sounds", "build a founder voice dossier", or "set our content pillars"; runs an 80%-extraction interview over the user's OWN posts, emails, and decks (never competitor scraping, never an invented persona) and produces the versioned voice record — a per-platform register map (incl. 小红书/微信公众号), banned phrases, per-context disclosure lines (the ECHO C2 upstream), a few-shot bank built exclusively from own posts, and 3-5 content pillars with Estimated %-allocations — submitted via memory/events/channels.ndjson for channel-registry to store as voice-dossier.md, the record every Craft-phase skill reads first. Not for the brand-level voice canon — use brand-language-codifier; not for audience/persona research — use audience-mapper. 声音档案/品牌语气/创始人语气/内容支柱/披露声明
The English summary is being prepared. Showing the original description.
Build a documented understanding of unfamiliar code before a security audit. It records function assumptions, guarantees, dependencies, and open questions, producing a dossier and individual function notes to support later vulnerability analysis.
Organize information about people, companies, and concepts into profiles with current summaries and dated histories. Extract details from meeting notes, connect related profiles, and retrieve past conversations to prepare for upcoming meetings.
Collect public evidence about a person, company, or topic with DeepAPI and save it as a structured JSON dossier. Source links, uncertainty checks, and coverage notes show what was found and what remains missing.
Génération de sujets d'entraînement complets pour l'épreuve de NOTE DE SYNTHÈSE (5 heures, coefficient 3) de l'examen d'accès au CRFPA : choix du sujet, dossier documentaire de 16 à 20 documents assemblé à partir de sources réelles vérifiées (textes, jurisprudence, travaux parlementaires, doctrine) avec contrôle du verbatim, puis grille de notation au modèle de la Commission nationale (résumé de chaque document, problématique, thèmes cotés sur 20, plan). Livraison en deux fichiers .docx distincts, le sujet et la grille. Si l'utilisateur n'impose pas de sujet, en chercher un dans l'actualité juridique. Mode aveugle pour l'étudiant qui compose sans rien voir du corrigé. Déclencher dès que l'utilisateur demande un sujet de note de synthèse, un dossier documentaire, une note de synthèse blanche, un entraînement à l'épreuve de 5 heures du CRFPA ou de l'IEJ, ou une grille de note de synthèse. NE PAS déclencher pour les épreuves de 3 heures (sujet-crfpa-toutes-matieres) ni pour la correction de copies.
The English summary is being prepared. Showing the original description.
Voert de iteratieve desk-review-&-completion-cyclus uit op een regelrecht-corpus — plannen, harvesten/migreren/uitbreiden, multi-agent valideren, bevindingen 4-weg classificeren (modellering-fout / wetgevings-fout / engine-limitatie / acceptabele untranslatable), synthese + heroverweging, documenteren (wetgevings-/stelselfouten-analyse, fixes-plan, engine-limitaties, diagrammen, corpus-status), verifiëren tegen externe bronnen (resolutie-tracker + bronnen-dossier), en een eindrapport per cyclus. Gebruik dit bij corpus-review op correctheid/coverage zonder live expert-sessie, het opstellen van een wetgevings-notitie-bron, schema-migratie, het harvesten van nieuwe wetten, of het aansturen van een autonome completion-loop. Dossier-agnostisch; de regelrecht-methode is de vaste taal. Voor live-validatie met experts: zie regelrecht-audit-products.
The English summary is being prepared. Showing the original description.
Bouwt de audit- en workshop-producten waarmee juridische experts een machine-leesbare (regelrecht-YAML) vertaling van wet- en regelgeving valideren in een live sessie. Gebruik dit bij het voorbereiden van een expert-workshop of validatie-sessie over een dossier, het maken van een scope-/stelselanalyse, per-artikel audit-checklists, facilitator-materiaal, testcase-scenario's, of sessie-verslagen (intern + extern). Dossier-agnostisch; de regelrecht-methode (YAML, formules, untranslatables, source/override, legal_basis, engine-trace) is de vaste taal. Voor analytische desk-review van een corpus zonder live sessie (wetgevings-/stelselfouten, coverage, multi-agent review): zie de zusterskill regelrecht-stelselanalyse.
The English summary is being prepared. Showing the original description.
Build a timeframe-bounded research dossier by decomposing a topic into year orchestrators and month-level research passes that each write one condensed paragraph plus sources directly into a target file. Use when the user asks for a dossier, timeline, chronology, release history, or month-by-month research bounded by specific years or months. Not for timeless explainers or single-document summaries with no temporal scope.
The English summary is being prepared. Showing the original description.
Build a dossier on a person: recall everything the vault already knows, map their public profiles by web research, emit a deep-research prompt for external tools, and persist a well-linked person card. Triggers: "/portret <name>", "dossier on <name>", "profile <name>".
The English summary is being prepared. Showing the original description.
Generates a structured research briefing for a topic or person as a Markdown scaffold (stdout or file). No persistent store.
The English summary is being prepared. Showing the original description.
Research competitors from their website URLs and turn findings into consistent Markdown profiles. Compare features, pricing, positioning, and available SEO data, with dated sources and a summary that brings multiple competitors together.
Prepare an industry briefing once a project's sector is defined. It covers sector context, potentially applicable regulations, familiar interface patterns, technology choices, and risks, while separating verified evidence from hypotheses and questions requiring further review.
Turn completed research, analysis, reports, or plans from the current session into a self-contained HTML artifact. A renderer controls layout, typography, and color, using structured content and a choice of two visual styles.
Research a defined topic within agreed limits and produce a cited report that distinguishes evidence, inference, contradictions, and gaps. Public web access requires consent, and saving findings or merging them into existing Obsidian notes receives separate review.
Use DeepAPI to search the web, collect website and social platform data, and produce sourced research. It also routes tasks to services for public website actions, email, image generation, and persistent agent memory.
[omh] Deep dive before a decision: deep research engine - grounding for specs and decisions: study open-source reference implementations with pinned refs, gather live web evidence with citation discipline, verify contested claims, and distill a decision-grounding dossier that planning consumes; for a decision brief use research-brief, for upstream guidance use web-research. Use when the user says: research plan, literature review, research literature, review recent papers, deep research, deep-research, exhaustive research, saturation research.
The English summary is being prepared. Showing the original description.
Use when the user asks to "codify our brand voice", "define naming rules for our products and tiers", or "write the tone-of-voice guide with banned phrases"; produces the brand-level voice canon (register, tone spectrum, banned-phrase list, few-shot examples drawn only from the brand's own published material) and the naming tax (product / feature / tier naming rules plus approved and banned terms) that seeds the narrative-registry canon and that every channel's voice adaptation points up to. Not for per-platform voice adaptation — use channel-registry's voice-dossier; not for finished copy or blog posts — use content-writer; not for the message hierarchy itself — use message-system-architect; not for claim adjudication — use offer-claims-registry. 品牌语气/词汇表/命名税/禁用词/品牌语言规范
The English summary is being prepared. Showing the original description.
Use when the user asks to "log this launch", query a launch date/embargo, record a stage transition, or update submissions/outcomes; curates launch facts through the append-only launches event stream with optimistic revisions and derived dossier/calendar views. Not for RAMP scoring — use launch-readiness-auditor; not for planning tier/window — use launch-tier-planner. 发布台账/发布日历/阶段与禁运期记录
The English summary is being prepared. Showing the original description.