「internal」の検索結果

Use when the user asks to "build a message house", "write a PR-FAQ for our launch", or "define the launch narrative and value pillars"; derives from the positioning canvas a message house — tagline, one-liner, three value pillars, per-persona proof points (each labeled Measured / User-provided / [needs source]) — plus a working-backwards PR-FAQ narrative spine (launch-day tense, empty-chair test, five external + five internal FAQs) and per-channel message angle packs (angles, not finished copy). Not for the positioning canvas itself — use positioning-mapper; not for finished blog posts or pages — use content-writer; not for ad or email units — use each discipline creative builder; not for claim adjudication — use offer-claims-registry. 消息屋/PR-FAQ/价值支柱/发布叙事

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

Use when the user asks to "analyze backlinks", "analyze my off-site signals", or "track AI traffic / ChatGPT / Perplexity referrals"; profiles referring domains, anchor-text mix, toxic links, and disavow candidates (backlinks mode) or isolates AI-assistant referral sessions in GA4/GSC/logs and reports their trend, landing pages, and AI-vs-organic conversion (ai-referrals mode). Not for internal links — use site-structure-optimizer; not for keyword positions — use rank-tracker; not for multi-metric stakeholder reports — use performance-monitor. 外链分析/反向链接/AI流量/AI引荐/ChatGPT流量/AI转化

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

Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

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

Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

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

Add redaction annotations to sensitive fields in schemas to block or hash PII. Use when configuring GDPR/HIPAA compliance, protecting credentials, or blocking internal fields from materializations. Use when user says "protect PII", "hide sensitive data", "hash field", "redact field", "GDPR compliance", "don't capture field", "remove field from Estuary", or "prevent Estuary from capturing field".

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

Create an Estuary derivation with custom SQLite state (internal tables) to make per-document decisions based on accumulated history — account balances, inventory levels, approval workflows, deduplication. Derivations add complexity and cost — confirm the user wants a derivation before reaching for this. Use when user says "stateful derivation", "derivation to track balance", "transformation to approve based on state", "derive an approval workflow", "deduplication derivation", or "build a stateful derivation".

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

Create an Estuary derivation that maintains a sliding time window of events (e.g. "transfers in the last 24h", "failed logins in the last 5 minutes") using internal SQLite state and readDelay for time-based expiration. Derivations add complexity and cost — confirm the user wants a derivation before reaching for this. Use when user says "windowing derivation", "derivation for last-24h events", "rolling-window derivation", "sliding-window transformation", "fraud-detection derivation", "rate-limit derivation", or "time-window derivation".

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

Control FriendlyBet operating cost, free-tier viability, provider/API cost, GitHub Actions/Supabase/Vercel usage, documentation hygiene, company memory updates, playbook maintenance, and skill validation. Use when evaluating cost, operational burden, tooling, internal docs, company memory, or whether agent profiles should become full skills.

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

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

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

Use when working with Budibase — budibase low-code platform management covering application inventory, table and datasource health, screen layout analysis, automation monitoring, and user role auditing. Use when reviewing internal app configurations, investigating data connectivity issues, monitoring automation runs, or auditing user access controls.

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

Use when working with Appsmith — appsmith low-code platform management covering application inventory, workspace organization, datasource health, page and widget analysis, and user access auditing. Use when reviewing internal tool configurations, investigating datasource connectivity, monitoring application deployments, or auditing workspace permissions.

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

Build high-quality MCP servers with strong tool design, structured outputs, clear error handling, and realistic evaluations. Use when creating or improving MCP servers in TypeScript or Python for external APIs, services, or internal platforms.

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

Guides migration of .NET Framework Thread.Abort usage to cooperative cancellation in modern .NET. USE FOR: modernizing code that calls Thread.Abort, catching ThreadAbortException, replacing Thread.ResetAbort, replacing Thread.Interrupt for thread termination, resolving PlatformNotSupportedException or SYSLIB0006 after retargeting to .NET 6+, migrating ASP.NET Response.End or Response.Redirect(url, true) which internally call Thread.Abort. DO NOT USE FOR: code that only uses Thread.Join, Thread.Sleep, or Thread.Start without any abort, interrupt, or ThreadAbortException usage — these APIs work identically in modern .NET and need no migration. Also not for projects staying on .NET Framework, or Thread.Abort usage inside third-party libraries you do not control.

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

Prepare a project for open sourcing: a sanitized fork with secrets and internal references stripped, a sanitizer verdict, README and LICENSE, then a new PRIVATE GitHub repo created and pushed only after GO. The playbook never makes the repo public. Use for "open source this project", "make a sanitized fork", "prepare a public release".

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

Workflow-state classification vocabulary for inter-team relay. Maps inbound signals from the remote agent to a routing decision. Intentionally narrow — states and destinations only.

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

HTTP Request Smuggling — frontend/backend HTTP parser uyumsuzluğunu sömürerek auth bypass, cache poisoning, internal endpoint erişimi

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

Tests APIs for excessive data exposure where endpoints return more data than the client application needs, relying on the frontend to filter sensitive fields. The tester intercepts API responses and analyzes them for leaked PII, internal identifiers, debug information, or sensitive business data that the UI does not display but the API transmits. This maps to OWASP API3:2023 Broken Object Property Level Authorization. Activates for requests involving API data leakage testing, excessive data e...

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

Tests APIs for injection vulnerabilities including SQL injection, NoSQL injection, OS command injection, LDAP injection, and Server-Side Request Forgery (SSRF) through API parameters, headers, and request bodies. The tester crafts malicious payloads targeting different backend technologies and injection contexts to extract data, execute commands, or access internal services. Maps to OWASP API8:2023 Security Misconfiguration and API7:2023 SSRF. Activates for requests involving API injection te...

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

Search the public web and crawl URLs via the Unique AI Platform's `unique-cli web-search` command, with automatic per-turn citation tracking so cited web facts render as clickable external reference chips and `<sup>N</sup>` footnotes on the Unique platform. ALWAYS use this skill when the user asks to search the public web, research a topic online, look up news/articles/regulations, fetch the contents of one or more URLs, or perform any "two-phase" web research (search → review snippets → crawl selected URLs for full content). Routes through the Unique AI Platform's `/web-search-api` endpoints, so the engine (Google, Brave, Tavily, Jina, Firecrawl, …) and crawler are resolved server-side from the current environment — you never need to manage engine API keys yourself. Use this instead of fabricating answers from training data whenever fresh / source-cited information is needed. Do NOT use this skill for the internal knowledge base (`unique-cli search`) or for arbitrary tool execution (`unique-cli mcp`).

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

SEO + GEO (AI-search) + brand-entity desk (Busabase App-in-Skill) — wired to Google Search Console for a dashboard over search analytics and an agent-prepared SEO opportunities review queue, plus an AI-visibility tracker (are we cited in ChatGPT / Perplexity / Gemini / Claude / Copilot answers), a GEO content-optimization queue gated by geo-qa, and an entity / knowledge-panel readiness checklist. Use when the user invokes $kelly-seo or /kelly-seo, mentions SEO, Google Search Console, GSC, search analytics, search performance, queries, keywords, rankings, positions, impressions, clicks, CTR, striking-distance queries, title/meta rewrites, content briefs, internal links, SEO opportunities review, GEO, generative engine optimization, AI search, AI visibility, being cited by AI answer engines, ChatGPT/Perplexity/Gemini/Claude/Copilot citations, brand entity, knowledge panel, Wikidata, schema.org, or entity readiness.

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

Legal precedent App-in-Skill (Busabase-backed) desk for internal casebase search, local court-pattern analysis, similar-case packs, citations, and approval-gated research exports. Use when the user invokes $kelly-legal-precedent-desk, mentions 类案检索, 本地裁判尺度, 内部案例库查询, 案例查阅与收藏, precedent research, similar cases, legal research pack, or wants a Busabase-backed desk where lawyers review agent-prepared precedent findings before reuse.

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

Legal matter-strategy App-in-Skill (Busabase-backed) desk for new-case strategy, issue trees, evidence checklists, risk analysis, pleading outlines, and approval-gated drafting packs grounded in internal precedents. Use when the user invokes $kelly-legal-matter-strategy, mentions 案件策略, 办案辅助, 证据清单, 争议焦点, 文书生成辅助, litigation strategy, arbitration strategy, pleading outline, or wants a Busabase-backed desk where responsible lawyers review agent-prepared strategy before use.

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

Legal casebase App-in-Skill (Busabase-backed) intake and anonymization QA desk for law-firm judgment and award documents. Use when the user invokes $kelly-legal-casebase-ingest, mentions internal case database, 智能案例库, 裁判文书入库, 脱敏, 结构化, 分类标注, 案例审核, 质量验收, or wants a Busabase-backed desk where reviewers approve, revise, or block agent-prepared case records before they become searchable knowledge assets.

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

Generates publish-ready LinkedIn posts for B2B SaaS marketing leaders writing from an operator point of view: real decisions, real trade-offs, real constraints, and defensible lessons. Use when turning an internal observation, framework, campaign decision, miss, or shipped artifact into a public LinkedIn post. Best for demand generation, ABM, marketing ops, product marketing, and SaaS GTM leaders building credibility through practical operating insight. Not intended for generic brand posts, company announcements, sales outreach, or long-form content.

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