Results for “data write”

Use this skill when a company needs rules for how staff use company systems, data, devices and AI tools, or asks "write our acceptable use policy", "AUP for employees", "can staff use ChatGPT at work", "AI usage policy", "BYOD rules", "remote work security rules" or "a policy people will actually read". Finds how people really work (devices, apps, AI tools, travel), puts the choices to the reader as decisions, drafts a short plain-language policy with concrete do and do not examples, and adds a comprehension check and an acknowledgement text for onboarding.

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

Use this skill when a company needs to know what AI it builds, buys or uses, before an AI governance programme, an AI regulation review or a customer questionnaire, and asks "list our AI systems", "build an AI register", "AI inventory", "where are we using AI", "find shadow AI", "which of our vendors use AI" or "what AI do we have before the AI Act". Discovers AI systems from procurement, single sign-on, code and teams, records one entry per use case with owner, purpose, data, affected people and the company's role, and writes a CSV register plus notes of borderline cases and open questions.

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

Use this skill when an internal auditor has one process or area to audit and needs a working checklist built from the company's own documents, or asks "build an internal audit checklist", "audit questions for access management", "what do I test in the supplier process", "audit plan for this area", "how many samples should I take", "internal audit of our data protection process" or "test our incident process against what the policy says". Turns each commitment in the company's policies and procedures into a test with a question, a record to inspect, a sample and a pass criterion, adds framework-specific checks through a lookup, and writes a checklist file the auditor fills in during fieldwork.

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

Writes and reviews Snowflake-specific SQL: QUALIFY, FLATTEN, VARIANT/OBJECT/ARRAY handling, streams, tasks, stages, and warehouse-aware patterns. Use when generic SQL is not enough on Snowflake — semi-structured data, incremental pipelines, or Snowflake DDL.

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

Writes and reviews dbt projects targeting Snowflake: models, schema.yml metadata, sources, tests, macros, and project structure. Use when building or reviewing dbt models, generating dbt YAML, or applying dbt best practices.

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

Interactive onboarding that learns your communication style, audiences, and data sources to configure personalized status briefings. Paste in examples of updates you already write, answer a few questions, and roundup calibrates itself to your workflow. Use the first time Roundup is used, or to recalibrate its style and sources.

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

TDD methodology for production-quality tests. Write tests FIRST driven by PRD, Tech Spec, Implementation Plan. Covers minimal mocking, realistic test data, strong assertions, test independence.

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

Conduct reproducible web searches and decision-oriented research across official sites, search engines, news, papers, forums, social platforms, and public datasets. Use when Codex must investigate a person, organization, product, market, technical resource, reputation, career choice, or other current topic; compare candidates; verify claims; collect dated citations; distinguish facts from inference and anecdote; or write an evidence-backed research report.

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

Audit and harden Convex authorization: identity-from-arg impersonation, missing per-document ownership checks, PII-leaking public queries, and writes into containers the caller doesn't own. Deterministic scan + canonical requireIdentity/requireOwner fix + tsc verify. Use for 'secure my app' / 'audit auth' / 'who can access this data', not generic code review.

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

Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.

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

Scrapes pump.fun/board using Chrome browser automation to extract the top 100 trending Solana tokens and writes structured markdown for a trading agent to consume. Use this skill any time you need to: scan pump.fun for new tokens, refresh the pump.md token list, run the scheduled board scrape, collect Solana meme token data, or build/update a trading watchlist from pump.fun. Even if the user says something casual like "check pump" or "update the token list" or "what's trending on pump", use this skill. The output file path and format are configurable but default to /Users/8bit/solanaos/pump.md.

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

Prepares the trend update for a recurring emailed report: identifies report emails not yet processed, extracts the configured metrics from their spreadsheet, CSV or PDF attachments, returns new rows for an append-only trends sheet and writes a DRAFT summary with period-on-period deltas and flagged anomalies. Use when the user asks to "update the trends for the weekly report", "analyse the latest monthly report", "what changed in the latest report", "do the latest numbers look unusual" or "set up tracking for a report that arrives by email". Do not use for a single file with no trend state, use dataset-insight-pack instead. Drafts for human review; never approves, authorises or signs off.

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

Drafts one knowledge article or known-error article from a resolved incident or ticket thread: symptoms as reported, environment, cause exactly as the resolver stated it, resolution steps as performed, workaround with its limits, verification, things tried without effect, related records, keywords and proposed metadata, every statement traced to a ticket note or marked UNKNOWN, with a redaction log and a question list for the knowledge owner. Never decides a root cause, adds a step or publishes. Use when the user asks to "write a KB article from this ticket", "turn this resolved incident into a knowledge article", "draft a known error record for this", "document the fix we just did" or "make this thread into a how-to for the service desk". Do not use for a procedure the team will execute (runbook, operating procedure, playbook), use runbook-drafter instead; for a post-incident review, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.

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

- Find internet-exposed hosts, ports, services and devices using third-party internet-scan data instead of touching the target. Use when asked what a company has exposed to the internet, to check open ports on an IP or netblock, or to write a Shodan filter query

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

Use this skill when creating executive-level briefing materials, board reports, management meeting presentations, or investor briefings. This skill provides the "So What? / Why Now? / What Next?" framework, data visualization guidelines optimized for executives, and professional templates for rapid document creation. Triggers include "create board report", "executive summary", "management meeting materials", "investor presentation", "one-page summary", or requests to communicate complex information to senior leadership.

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

Translate a fuzzy analytical question into a rigorous investigation plan. Interrogates the ask, grounds the plan in the available data dictionary, applies analytical best practices, and produces a structured brief of query specifications for a downstream query-writing skill. Plans, does not write SQL. Use when: "why did X drop", "is there a relationship between A and B", "who are our highest-value customers", "what's driving the change in Y", "investigate this trend", "design an analysis for", "scope this analytical question". (narrative-common)

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

Discover and normalize entities for programmatic SEO from a seed keyword or CSV file. Writes normalized entities to data/entities.json. Use when the user wants to find, import, or expand a list of SEO targets.

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

Datasets : ProntoQA, FOLIO, ProofWriter, ConditionalQA, StrategyQA Model : GPT-5 (Azure deployment) Config : max_attempts=3 , verify_timeout=10000ms B

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

WooCommerce Memberships storage and relationship map for membership plan CPTs, user membership CPTs, post statuses, plan/user membership meta keys, rule storage, profile-field storage, order grant meta, and WooCommerce Subscriptions-linked memberships. Use when code reads or writes wc_membership_plan, wc_user_membership, wcm-* statuses, wc_memberships_rules, _subscription_id, _has_installment_plan, _free_trial_end_date, membership plan access meta, user membership dates, product/order grant meta, or when an agent needs exact Memberships CPT/meta names and the Memberships-Subscriptions relation.

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

Produces WordPress draft posts from research findings — converts Paper Store research records or raw research data into publishable blog posts, buying guides, brand spotlights, and how-to articles. Use when the task asks to "turn research into a post", "create a blog post from findings", "publish my research", "research to content", or "write up the findings". Covers the full research-to-post pipeline with Paper Store integration.

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

Use when the user asks to "package the launch assets", "build a press kit", or "prep the store listing and go-live checklist"; produces a tier-scoped launch asset manifest with production status — a press kit spec (factsheet, description, history, features, videos, images, logo and icon, awards, contact), demo script and screenshot specs, a launch FAQ, dual-store listing metadata drafts against the official character budgets (per App Store Connect / Play Console documentation), and a technical go-live checklist manifest (robots flip, sitemap, OG tags, analytics verification — execution stays with technical-seo-checker and serp-markup-builder). Not for the message copy itself — use message-house-builder or content-writer; not for landing page UX — use landing-optimizer; not for keyword research beyond the store surfaces — use keyword-research. 发布资产打包/press kit/商店listing规格/上线检查清单

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

Use when the user asks to "build programmatic SEO pages", "generate pages at scale", "rank on a high-authority third-party site", "borrow domain authority", "build a vs / alternative page", "do local SEO", "optimize a Google Business Profile", or "fix NAP" — one page-build router with four modes: programmatic (template × dataset systems), parasite (barnacle publishing on Medium/Reddit/LinkedIn/GitHub), comparison (vs / alternative pages in four formats), and local (GBP + NAP + citations + location pages), each with its own thin/duplicate, honesty, or reputation-abuse guardrail. Not for finding what to target — use keyword-research or content-gap-analysis; not for drafting one standalone article — use content-writer; not for scoring a page for publish — use content-quality-auditor. 程序化SEO/批量页面/寄生SEO/借势权重/对比页/vs页/替代页/本地SEO/谷歌商家档案/NAP一致性

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

Account-based marketing for B2B SaaS. Use this skill to build a target account list, tier it 1:1 / 1:few / 1:many, size it against sales capacity, turn intent and engagement signals into plays, write the multi-channel orchestration contract each tier runs on, and measure the program in account coverage, penetration and pipeline instead of MQLs. Also triggers on: ABM, account-based marketing, target account list, TAL, named accounts, account tiering, 1:1 ABM, one-to-few, programmatic ABM, account selection, ideal customer profile fit, intent data, buying signals, 6sense, Bombora, Demandbase, account penetration, account coverage, sales and marketing alignment on accounts, enterprise account program.

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

Control risky structural change by proving a refactor is necessary and that behaviour, contracts, data, security boundaries, and operational properties can be preserved through a staged migration. Use whenever the user wants to refactor, restructure, clean up, modernise, extract, migrate, rewrite, or re-architect existing code, or asks whether they should. Prefer this over starting the refactor. DO NOT REFACTOR is a first-class outcome. Part of the audit suite; inherits the shared constitution while its own job is proving necessity and behavioural preservation.

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