Results for “open source”

Drafts an account plan from the CRM notes, emails, meeting notes and contracts the user provides: situation, stakeholder map, opportunities as recorded, risks, open commitments and proposed next actions, every line traced to a source and gaps marked UNKNOWN. Returns a DRAFT Markdown document in the chat. Use when the user asks to "build an account plan", "refresh the key account plan", "what do we know about this account", "account review for <customer>" or "what should happen next on this account". Do not use for preparing a first call with a prospect, use discovery-call-prep instead; for scoring inbound leads against a rubric use lead-qualification-scorer. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Turns a campaign idea, its objectives and the supporting notes (audience material, offer facts, budget and dates, channel list) into one DRAFT one-page campaign brief: objectives, audience, one single-minded message with sourced proof points, channels and timeline, success measures with baselines, mandatories, risks and numbered open questions for the campaign owner. Use when the user asks to "write a campaign brief", "draft a creative brief for this launch", "turn this idea into a one-page brief", "tighten this brief to one page" or "build the marketing brief from these notes". Do not use for a message house, messaging pillars or a launch narrative on its own, use message-house-builder instead; for laying the campaign onto dated slots, use content-calendar-planner. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Builds a DRAFT content calendar for a stated period from the themes, channels, cadence rules, fixed dates and owners the user provides: one dated row per planned item with theme, channel, format, working title, owner, status and source, plus a cadence check with its arithmetic, theme balance, owner load and the slots left open. Use when the user asks to "build the content calendar for Q4", "lay these themes onto dates", "plan a month of posts across our channels", "extend the editorial calendar" or "check this calendar against our cadence". Do not use for deciding what the campaign says or why it runs, use campaign-brief-builder instead; for writing the items themselves, use announcement-drafter or internal-newsletter-drafter. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Turns one meeting transcript or recap into a DRAFT action-items document (decisions, owned and dated action items with verbatim source quotes, open questions), a task list ready for the user to enter into their task tracker, and one DRAFT follow-up email per action owner, all returned in the chat for the user to store, create or send. Use when the user shares, names or points to a meeting transcript or recap and asks to "pull the action items from this transcript", "who owns what after today's call", "draft follow-up emails to each owner" or "turn this recap into tasks". Do not use for full minutes, use meeting-minutes-writer instead; a brief before a meeting is meeting-prep-onepager. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Turns process notes, a walkthrough or interview transcript, a transcript of a meeting recording or a stale existing procedure into a draft standard operating procedure: purpose and trigger, scope, definitions, roles with a RACI table, numbered steps with the check that closes each one, records produced, controls as stated, and open questions for the process owner. Every step traces to the source or reads UNKNOWN. Use when the user asks to "write an SOP from these notes", "turn this walkthrough into a procedure", "document how we do this", "draft the standard operating procedure for", "build a RACI for this process" or "tidy up this old procedure". Do not use for technical runbooks with commands and rollback, use runbook-drafter instead; for meeting minutes and action lists, use transcript-to-actions. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Turns one meeting transcript, recording recap or set of raw notes into concise DRAFT minutes returned in the chat as a single Markdown document: header metadata, attendance and apologies, agenda items each with a short neutral summary and outcome, numbered decisions with an owner, numbered action items with owner and due date, open questions, carried-over actions and the next-meeting line, every entry backed by a short verbatim source fragment and every missing fact marked UNKNOWN. Use when the user asks to "write the minutes", "draft minutes from this transcript", "turn these notes into meeting minutes", "produce the minutes of meeting for today's call", "tidy my rough minutes into the standard format" or "prepare the minutes for circulation". Do not use for extracting action items, task lists or per-owner follow-up emails alone, use transcript-to-actions instead. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

- Entry point for open-source intelligence, investigation and verification work. Use when asked to investigate, research, verify, vet, check out, look up, background-check, trace, attribute or find someone or something; when a request involves due diligence, KYC or KYB, counterparty or vendor risk, sanctions and PEP screening, AML, fraud, business email compromise

The English summary is being prepared. Showing the original description.

Open-source one slice of a private system: take a component, sanitize it, run a leak-scan as a hard gate, publish to GitHub, then changelog, roadmap and tag on cadence, then the content wave. Publishing without passing the leak-scan is forbidden. Triggers: "/release-slice <piece>", "ship the next slice".

The English summary is being prepared. Showing the original description.

Watch incoming feedback from outside engineers on your open-source repos: comments, reviews, issues, mentions. Use when you need to find who replied to your pull requests or issues, triage human versus bot responses, and answer within a day with evidence.

The English summary is being prepared. Showing the original description.

Compare your data to a partner's data in the marketplace. Given a dataset you already own with person/edge data, this skill walks you through picking a partner data source to match against, choosing which identifier types to match on, optionally selecting which enrichment attributes to attach, and then submits the report — returning overlap, match counts, and demographic coverage. Use when: "how does my data compare to your marketplace", "compare my data to [partner]", "how much overlap do I have with [supplier]", "run a match report", "match my customers against 3P data", "see what enrichment is available for my dataset", or any open-ended question about marketplace overlap. (narrative-identity)

The English summary is being prepared. Showing the original description.

Reconstructed reference notes on EU and UK medical-device software, built from six sources captured 2026-10-13: MDCG 2019-11 rev.1 (June 2025), MDCG 2020-6 (April 2020), MDCG 2020-13 (July 2020), MDCG 2020-7 (April 2020), MDCG 2020-8 (April 2020), and the MHRA software-applications guidance (2023-07-01) with its stand-alone software PDF. Use for SaMD qualification and classification, legacy-device clinical evidence, the clinical evaluation assessment report, the PMCF plan, and the PMCF evaluation report, under EU MDCG guidance or UK MHRA guidance. SCOPE LIMITS: EU MDR and UK MHRA device software only; no IEC 62304, ISO 13485, or ISO 14971 text; no MDR or IVDR regulation body text; MDCG guidance is not legally binding; MHRA guidance is UK-specific; synthesized notes, not legal advice. LICENCE: Per-document: European Commission reuse policy (Decision 2011/833/EU, CC BY 4.0, attribution and indication of changes) for the MDCG documents; Open Government Licence v3.0 for the MHRA guidance; reconstructed notes with attribution; official PDFs not redistributed.

The English summary is being prepared. Showing the original description.

Signpost (not a knowledge pack) for maritime safety and class rules: SOLAS Consolidated Edition 2024 (IH110E) as the paywalled statutory core, ISM Code & Guidelines 2018 (ID117E), ISPS Code 2003 (K116E) and the 2021 guide (IB116E), and COLREGS 2026 (IC904E), with designation, edition, owner, status, and official URL only. Contains no source content. Free-path layers are US flag implementation (eCFR Title 46 and USCG circulars), the USCG Navigation Rules PDF, UK MCA notices under Open Government Licence v3.0, and class portals (DNV, ABS, Bureau Veritas). None of those layers is the IMO consolidated text. No in-repo pack covers these instruments.

The English summary is being prepared. Showing the original description.

Knowledge pack synthesized from JSP 376 Defence Acquisition Safety Policy V1.1 (April 2024, Ministry of Defence, Open Government Licence v3.0): acquisition safety requirements, safety artefacts, and their application across the standard acquisition lifecycle. Covers the policy frame and legislative baseline, SRO and User responsibilities, safety management and safety requirements, test and evaluation and the safety case, supervision and approvals decision support, and the seven lifecycle phases. SCOPE LIMITS: single-source (JSP 376 V1.1); MOD policy and guidance, not statute; builds on JSP 815 and cites JSP 655, neither reproduced here (use jsp-815 for the SMS); Chapter 4 (Non-Standard Acquisition) is unpublished in V1.1 and is not in this pack; no DEF-STAN text (Def Stan 00-056 is named, not quoted); no other JSP reproduced. Reconstructed reference notes, not MOD guidance, and no official status.

The English summary is being prepared. Showing the original description.

Knowledge pack reconstructed from JSP 815 Defence Safety Management System V1.3 (Ministry of Defence, Open Government Licence v3.0): the SMS Framework, all 12 Elements with their Expectations and Performance Statement themes, and Annexes A to F plus H. Covers the Defence Safety Function and which JSP applies, leadership and safety culture, organisation and SEMS applicability, legislation and exemption certificates, risk assessment and safety cases, supervision and contracting, competence and letters of delegation, equipment and infrastructure safety, performance and incident management, and assurance, audit, and the ISO 45001 clause mapping. SCOPE LIMITS: single-source (JSP 815 V1.3 with Annex H V1.2); carries no DEF-STAN 00-051 or DEF-STAN 00-970 content, no JSP 375, JSP 816; acquisition safety policy is in jsp-376, no Annex G (Assurance Toolkit), and no ISO 45001 text (clause numbers only). This pack is reconstructed reference notes, not MOD guidance, and has no official status.

The English summary is being prepared. Showing the original description.

Prepare, generate, proofread, and hand off captions for an approved video without hiding transcription uncertainty or changing the source cut.

The English summary is being prepared. Showing the original description.

Find useful moments in long-form video, create ranked short clips, reframe them, and generate captions without losing source provenance.

The English summary is being prepared. Showing the original description.

Turn an approved meme idea, image, or short source into a concise humorous video draft with a clear hook, caption plan, and platform variants.

The English summary is being prepared. Showing the original description.

Turn an authorized long-form video into a ranked set of YouTube Shorts candidates with vertical framing, captions, timestamps, and source provenance.

The English summary is being prepared. Showing the original description.

Signpost (not a knowledge pack) for the systems-engineering standards landscape — ISO/IEC/IEEE 15288, 24748, 29148, 42010, 15026, 24765; INCOSE SE Handbook & Vision 2035; OMG SysML; SAE/EIA 1001/649/748; ECSS space standards; NATO AAP-48; CMMI; NIST SP 800-160; and more. Contains NO source content: it lists each standard's designation, title, purpose, owning SDO, whether it's redistributable, and where to get it. Use when you need to identify or locate an SE standard — most are paywalled/all-rights-reserved and cannot be packaged, so this points you to the owner (and to the open packs where one exists).

The English summary is being prepared. Showing the original description.

Signpost (not a knowledge pack) for the automotive standards landscape: ISO 26262, ASPICE, SAE J3016, UNECE R155, UNECE R156, and the NHTSA vehicle set. Contains NO source content: designation, edition, owner, status, and an official catalogue URL only. Use when you need to identify or locate an automotive standard. Most are paywalled or carry no redistribution grant and cannot be packaged; the one open path is the nhtsa-vehicle pack.

The English summary is being prepared. Showing the original description.

Signpost (not a knowledge pack) for the functional safety standards landscape: IEC 61508, ISO 26262, ISO/SAE 21434, UL 4600, SAE J3016, and ASPICE. Contains NO source content: designation, edition, owner, status, and an official catalogue URL only. Use when you need to identify or locate a functional safety standard. All six are paywalled or carry no redistribution grant and cannot be packaged; open paths point at US Government packs, which are not equivalents.

The English summary is being prepared. Showing the original description.

Use when contributing to the CopilotKit open-source project — forking, cloning, setting up the monorepo, creating branches, running tests, and submitting pull requests against CopilotKit/CopilotKit.

The English summary is being prepared. Showing the original description.

Build, run, and manage OCI/Linux containers as lightweight per-container VMs on Apple-silicon macOS using Apple's open-source container CLI, no Docker daemon required.

The English summary is being prepared. Showing the original description.

Migrate a .NET 9 project or solution to .NET 10 and resolve all breaking changes. USE FOR: upgrading TargetFramework from net9.0 to net10.0, fixing build errors after updating the .NET 10 SDK, resolving source and behavioral changes in .NET 10 / C# 14 / ASP.NET Core 10 / EF Core 10, updating Dockerfiles for Debian-to-Ubuntu base images, resolving obsoletion warnings (SYSLIB0058-SYSLIB0062), adapting to SDK/NuGet changes (NU1510, PrunePackageReference), migrating System.Linq.Async to built-in AsyncEnumerable, fixing OpenApi v2 API changes, cryptography renames, and C# 14 compiler changes (field keyword, extension keyword, span overloads). DO NOT USE FOR: .NET Framework migrations, upgrading from .NET 8 or earlier (use migrate-dotnet8-to-dotnet9 first), greenfield .NET 10 projects, or cosmetic modernization. LOADS REFERENCES: csharp-compiler, core-libraries, sdk-msbuild (always); aspnet-core, efcore, cryptography, extensions-hosting, serialization-networking, winforms-wpf, containers-interop (selective).

The English summary is being prepared. Showing the original description.