「repo」の検索結果

Designing data stories and narrative-driven analytics in Salesforce: structuring CRM Analytics dashboards for executive communication, text widgets and conditional highlights for annotation, sequential narrative in Tableau Story sheets, and Einstein Discovery narrative REST endpoints. Trigger keywords: data storytelling dashboard, executive analytics narrative, CRM Analytics text widget annotation, Tableau story sheet, smart data discovery narrative API. NOT for building the Einstein Discovery story or prediction definition - use admin/einstein-discovery-setup. NOT for choosing between Reports, CRM Analytics and Tableau - use admin/einstein-analytics-basics.

日本語の概要は準備中です。原文の説明を表示しています。

Author the Salesforce Configuration Workbook — the structured, reviewable handoff document an admin uses to execute a feature across Objects/Fields, Page Layouts, Profiles/PSGs, Sharing, Validation, Automation, List Views, Reports, Integrations, and Data. Triggers: 'salesforce configuration workbook', 'admin handoff document', 'implementation workbook'. NOT for object design itself (use admin/custom-field-creation, admin/lookup-and-relationship-design, agents/object-designer/AGENT.md), NOT for permission set design (use admin/permission-set-architecture, agents/permission-set-architect/AGENT.md), NOT for Flow construction (use skills/flow/* and agents/flow-builder/AGENT.md), and NOT for the deployment manifest (use skills/devops/metadata-api-retrieve-deploy). More triggers: workbook row schema, recommended_agent, recommended_skills, row_id, source_req_id, RTM linkage block, not-in-scope-this-release, descope ledger, version-lock the workbook, check_workbook.py.

日本語の概要は準備中です。原文の説明を表示しています。

Compound fields (Name, Address, Geolocation): SOQL access rules, DML semantics, component access in Apex/LWC, reporting column behavior, formula field restrictions. NOT for creating a new custom field — use admin/custom-field-creation. NOT for formula syntax and functions — use admin/formula-fields. Trigger keywords: BillingAddress, MailingAddress, ShippingAddress, StateCode, CountryCode, GeocodeAccuracy, Location field type, displayLocationInDecimal, __Latitude__s, __Longitude__s, DISTANCE, GEOLOCATION, Custom Address Fields, AddressSettings, System.Address, System.Location, Person Account name.

日本語の概要は準備中です。原文の説明を表示しています。

Designing Campaign Hierarchy for program-level ROI tracking, configuring Customizable Campaign Influence (CCI) attribution models, and interpreting multi-touch attribution from MCAE B2B Marketing Analytics. Trigger keywords: campaign ROI, attribution model, campaign hierarchy, first-touch, last-touch, multi-touch, CCI, campaign influence, revenue attribution, campaign member status. NOT for deciding which attribution model and KPIs to adopt before any config - use admin/marketing-reporting-requirements. NOT for MCAE connector setup or the campaign sync that writes Campaign Member records - use admin/mcae-pardot-setup. Also covers: CampaignSettings, enableCampaignInfluence2, enableAutoCampInfluenceDisabled, enableB2bmaCampaignInfluence2, enableAccountsAsCM, CampaignInfluenceModel metadata, isDefaultModel, isModelLocked, recordPreference, AllRecords, RecordsWithAttribution, CampaignInfluence.RevenueShare, ModelType, CampaignMemberStatus IsDefault HasResponded SortOrder, HierarchyActualCost, HierarchyAmountWonOpportunities, TotalNumberofResponses, Opportunity.CampaignId primary campaign source.

日本語の概要は準備中です。原文の説明を表示しています。

Use when creating or managing CRM Analytics datasets: configuring dataflows, scheduling refreshes, selecting fields, handling date types, managing row-count growth, or troubleshooting stale or broken datasets. Triggers: 'dataset creation', 'dataflow schedule', 'dataflow quota', 'date field not filterable', 'dataset row limit', 'CRM Analytics data refresh', 'field type mismatch in dataset'. NOT for making an existing dataset smaller or faster — use data/analytics-dataset-optimization. NOT for choosing between Reports, CRM Analytics and Tableau in the first place — use admin/einstein-analytics-basics.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when planning user adoption, structuring Salesforce training materials, drafting release communications, or running a change impact assessment for a Salesforce rollout or update. Triggers: user adoption plan, training materials, release announcement, change impact, go-live communication, communication plan, training plan by persona, adoption metrics, LoginHistory adoption report, PromptAction, training sandbox, go-live checklist, post-go-live feedback, super user program, pilot group. NOT for org deployment mechanics or sandbox promotion — use admin/change-management-and-deployment. NOT for adoption of an Agentforce or Einstein AI feature — use admin/ai-adoption-change-management. NOT for configuring the in-app prompts themselves — use admin/in-app-guidance-and-walkthroughs.

日本語の概要は準備中です。原文の説明を表示しています。

Verify, customize, or opt out of moflo's AUTOMATIC durable-learning sharing across git worktrees / Conductor workspaces on one machine. As of the worktree-auto-sharing change this is on by default — learnings converge across a repo's worktrees with no setup. Use when the user asks "is memory shared across my worktrees?", "where are my worktree learnings stored?", "turn off worktree memory sharing", "share learnings across my separate clones", or "point my worktrees at a custom store". For a team or cross-machine (git-tracked) sharing, use /memory-team instead.

日本語の概要は準備中です。原文の説明を表示しています。

Guided setup for sharing moflo's durable learnings through a git-tracked JSONL artifact — for a whole TEAM on one repo, OR for one person across several MACHINES (a team of one). Use when the user says "share learnings with my team", "commit our moflo memory", "sync memory across my laptop and desktop", "set up memory.team_artifact", or "auto-export learnings on every PR". Installs a pre-commit hook so the artifact rides along in every commit. For many worktrees on ONE machine, use /memory-worktree instead.

日本語の概要は準備中です。原文の説明を表示しています。

Detects absence of a content moderation service integration for apps that accept user-uploaded media or posts, enforcing Guideline 1.2's requirement for timely response to content reports.

日本語の概要は準備中です。原文の説明を表示しています。

Detects missing report, block, filter, and contact information mechanisms required for all apps with user-generated content under Guideline 1.2.

日本語の概要は準備中です。原文の説明を表示しています。

Create a new package in the One Page monorepo with the required LICENSE symlink, README, and workspace registration. Use when adding a new core or feature package.

日本語の概要は準備中です。原文の説明を表示しています。

Generic automated semantic versioning and release workflow. Handles version increments, git tagging, GitHub releases, and automated changelog generation for any repository.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate the remote rules registry — the shared registry (often connected as a local folder or git repo) that the project's rules are published to and pulled from. Three modes, picked from the user's wording: create scaffolds a new local rules registry ("create a local rules registry", "init a rules registry"); update migrates/promotes local knowledge-base rules from .unikit/memory/ into the remote registry with automatic semver bumps ("migrate local rules to the remote registry", "promote my rules to the registry", "push local rules", "publish local rules", "update the rules registry"); sync pulls registry updates back into memory ("sync the rules registry", "pull registry updates"). Pass "--module <id>" to scope to one knowledge-base module. This skill ONLY orchestrates the CLI (`unikit-ai rules *`) — it never edits .unikit.json or .unikit/memory/ sources directly.

日本語の概要は準備中です。原文の説明を表示しています。

Qualitative quality review of game design documents — answers "is this design good, and does it follow best practices?" — across all three GDD axes: systems, flows, and content types. Fans out adversarial lenses (completeness, clarity, pillar alignment, systems-math, fantasy-delivery, feasibility, scope) plus domain lenses that check it against the game-design rules, each prompted to find problems rather than validate; produces a severity-graded verdict and a two-bucket report (apply-ready fixes vs research), handed to /unikit-gd-apply or /unikit-gd-explore in one move. Scope is inferred: a named system, flow, or content type reviews that document; "all" runs a cross-document review. Use when the user wants a critique, quality judgment, or rules check of the design, e.g. "review the combat GDD", "review the onboarding flow". This is the subjective quality pass — for a mechanical consistency check (numbers, terms, IDs, references matching the registry) use /unikit-gd-verify.

日本語の概要は準備中です。原文の説明を表示しています。

Research and ideation partner for GAME DESIGN — think through design ideas before writing them into the GDD; produces a brief, never edits the GDD itself. Use to assess a genre or market for viability, dissect a reference game (mechanics → dynamics → aesthetics), explore how to improve or extend an existing system, flow, or content type, research new mechanics the design lacks, investigate a part of the GDD in code, or develop the research bucket of a /unikit-gd-review report into decided edits. Trigger on "explore how to improve the flow", "ways to improve the combat system", "is this genre saturated", "break down the combat of Hades", "work out the review's open questions". GAME-DESIGN research only — for CODE or technical research use /unikit-explore; to reconstruct a design from code use /unikit-gd-recon; to write a change into the GDD use /unikit-gd-system or /unikit-gd-spec; to apply edits you know use /unikit-gd-apply; to invent a new game use /unikit-gd-brainstorm.

日本語の概要は準備中です。原文の説明を表示しています。

Dispatch an explicit, user-dictated set of edits that spans TWO OR MORE zones of the GDD — the master spec, systems, content types, and flows — in one ordered pass. Writes nothing itself: it resolves each delta to its (target, zone), orders them so a system change lands before the content or flow that depends on it, delegates each to the owning skill (/unikit-gd-spec, /unikit-gd-system, /unikit-gd-content, /unikit-gd-flow), and closes with one /unikit-gd-verify pass. Use when you already know the changes and they touch more than one part of the design, e.g. "apply these GDD changes", "update the combat system and its loot and the boss flow". It also takes a /unikit-gd-review report file (applies its apply-ready bucket), and a bare /unikit-gd-apply reads the last /unikit-gd-verify output in the session. For a single-zone change call its owner directly; to research an open question use /unikit-gd-explore first.

日本語の概要は準備中です。原文の説明を表示しています。

Record a finding about the configured engine MCP server into .unikit/MCP-RECHECK-NOTES.md — the project's log of what has to be re-checked here. Use right after a call reported success while changing nothing, ate an argument, or validated a broken state, e.g. "write this down", "record this MCP finding", "the server lied — note it", "add a recheck note", "trap this". Takes three forms of input: the finding in one line, a path to a plan file (harvests the "## MCP Findings" table of that plan and nothing else), or nothing at all — then it takes findings already in the session first, and offers to scan the tables of plans touched since the last audit. The table only, never the plan body. Writes in the one allowed genre — a check to perform; never a lifted gate, never a named workaround, never a claim about what the server can or cannot do. Makes zero MCP calls and needs no editor. To replay, retire, or upstream existing notes use /unikit-mcp-audit instead.

日本語の概要は準備中です。原文の説明を表示しています。

สร้าง test case ครอบคลุม edge case พร้อม bug report template และ regression checklist

日本語の概要は準備中です。原文の説明を表示しています。

Outbound SDR (Sales Development Representative) operating system that runs the full top-of-funnel motion across HubSpot (CRM, engagement, and source of truth) and Exa (web research + signals). Use this skill WHENEVER the user is doing outbound sales development, building target/prospect lists, defining or refining an ICP, enriching leads, researching accounts or people before outreach, writing cold emails or multi-touch sequences, qualifying or scoring leads, logging activity to CRM, handing meetings off to AEs, or reporting on pipeline. Trigger it even when the user only says things like "find me 50 leads", "research this account", "write a cold email to this person", "score these leads", "log this in HubSpot", or "build a sequence"; these are all SDR tasks this skill governs. Do not wait for the user to say "SDR" or "prospecting" explicitly.

日本語の概要は準備中です。原文の説明を表示しています。

Fix data that has gone wrong and change shape without breaking what reads it: duplicates, nulls, inconsistent document shapes, a field that means two things, a column that has to change. Use when a report cannot be built because the data is not in the right shape, when duplicates, nulls or inconsistent shapes are producing wrong numbers, when a field is needed or has to change, before a migration, or when onboarding data from a new source that does not match the standard shape.

日本語の概要は準備中です。原文の説明を表示しています。

Write the SQL or MongoDB query that answers a question and keeps answering it: the right grain, no fan out, parameterised window, checked against something known. Use when a number is needed that no report carries, when an existing query returns something that looks wrong, when a query is slow or expensive, or when somebody asks for a one off pull.

日本語の概要は準備中です。原文の説明を表示しています。

Reporting workflow for a working journalist, using web research and Apify's X scraper (social signals). Onboards the journalist, monitors their beat and builds digests, evaluates story pitches, finds and vets sources, and prepares interviews. Use for any newsroom task, such as "what's new on my beat", "is this pitch any good", "who should I talk to about X", "prep me for this interview", or "turn these notes into a draft".

日本語の概要は準備中です。原文の説明を表示しています。

Build the upload archive for a plugin payload in this distribution repository. Use when asked to package the plugin, produce the submission zip, cut a plugin release artifact, or prepare a Codex/OpenAI Plugin Portal upload. Covers host selection, the pre-flight gates, and what to do after the archive exists.

日本語の概要は準備中です。原文の説明を表示しています。

Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.

日本語の概要は準備中です。原文の説明を表示しています。