[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M734NAZPBRRG6T1F6MJW1CZF":3,"skill-same:01M734NAZPBRRG6T1F6MJW1CZF":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M734NAZPBRRG6T1F6MJW1CZF","productize-explore-data",null,"Profile and explore a dataset to understand its shape, quality, and patterns. Use when encountering a new table or file, checking null rates and distributions, spotting duplicates or suspicious values, or deciding which dimensions and metrics to analyze.","itseffi\u002Fproductize","itseffi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F15998472?v=4","01M734C5RJ7CKRTPB3FX84VZV7","Effi","01M734C5S6B7FW62ZNWYBZ9GG7",3,"MIT","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-explore-data\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: productize-explore-data\ndescription: >-\n  Profile and explore a dataset to understand its shape, quality, and patterns. Use when\n  encountering a new table or file, checking null rates and distributions, spotting duplicates\n  or suspicious values, or deciding which dimensions and metrics to analyze.\n---\n\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# Explore Data\n\n## Productize Preamble\n\nBefore producing the artifact, implementation step, or code change, classify the work:\n\n- **User\u002Fpersona**: founder, product leader, AI PM, AI builder, stakeholder, or mixed\u002Funknown.\n- **Product stage**: idea, validation, PMF search, growth, scale, pivot, or unknown.\n- **Artifact mode**: strategy memo, PRD, research plan, positioning, experiment, deck, roadmap, execution brief, diagnostic, or decision record.\n- **Artifact format**: Markdown for short, repo-native, diff-sensitive artifacts; self-contained HTML for long, visual, shareable, interactive, or explicitly requested artifacts.\n- **Evidence standard**: what is known, assumed, missing, and risky.\n- **Decision mode**: recommend, ask for a blocking input, or proceed with explicit assumptions.\n\nOperating rules:\n\n1. Do not produce generic product strategy filler. Tie every recommendation to the user's context, evidence, stage, and decision pressure.\n2. Separate facts from assumptions. Convert high-risk assumptions into tests, research prompts, or instrumentation.\n3. Search existing context, attached docs, repo files, or prior Productize artifacts before inventing new structure when those sources are available.\n4. Ask only for inputs that materially change the output. If the next step is obvious, proceed and state assumptions.\n5. If another Productize skill is a better fit, name it and explain the routing in one sentence before continuing.\n6. Enforce the output contract for this skill. Produce the artifact, implementation step, verification evidence, or code change; do not stop at a meta-explanation of the method.\n7. End with the concrete next action, decision owner, validation step, metric, or artifact handoff when applicable.\n8. Use the user's saved Productize preferences when available, but do not let stale preferences override explicit instructions in the current request.\n9. If you must ask a blocking question, use this compact format: `AskUserQuestion: \u003Cone question> Why it matters: \u003Cdecision it changes>`.\n10. Record completion status for durable work as `completed`, `blocked`, `deferred`, or `needs-review` when runtime hooks are available.\n\nArtifact format policy:\n\n- Default to Markdown for short notes, repo-native documentation, changelog fragments, or artifacts where clean source diffs matter.\n- Use a self-contained HTML file when the user asks for HTML, the artifact is likely to exceed about 100 lines, the reader needs diagrams\u002Ftables\u002Fcomparisons\u002Fscreenshots, the artifact is meant to be shared, or interaction\u002Fexport controls would help the user stay in the loop.\n- Route by product job first, then choose the format. Do not create a generic HTML workflow when a Productize playbook, gate, or routed skill owns the work.\n- HTML artifacts must be local-first and portable: one file, embedded CSS\u002FJS, no remote dependencies unless explicitly requested, readable without a dev server, responsive, accessible, and easy to skim.\n- Prefer semantic sections, tables, SVG diagrams, annotated code blocks, status chips, collapsible detail, and copy\u002Fexport buttons when they improve review speed. Avoid decorative complexity that hides the decision.\n- For implementation work with ambiguities, use `$implementation-notes` when the user asks for a running notes file, especially `implementation-notes.html` or `implementation-notes.md`.\n\nRuntime hooks, if available:\n\n- Use `productize-workflow start \"\u003Cuser request>\"` at the beginning of durable product work; it restores context, routes the request, records the session, and returns the required artifact contract.\n- Use `productize-workflow complete --id \u003Cid> --status completed|blocked|deferred|needs-review --artifact-type \u003Ctype> --summary \u003Csummary>` before ending durable product work; it records the artifact, saves context, and logs completion status.\n- Use `productize-update-check --strict` at the start of maintenance, setup, release, or generated-output work.\n- Use `productize-config` to read or write user\u002Fteam preferences such as persona, artifact mode, evidence threshold, or update-check policy.\n- Use `productize-session-log` to record important workflow decisions.\n- Use `productize-artifact-log` when a durable artifact is produced.\n- Use `productize-context-restore` before restarting long-running product work from scratch.\n- Use `productize-context-save` after producing a durable strategy, research, spec, or stakeholder artifact.\n- Use `productize-registry-search` or `productize-skill-router` when routing is ambiguous.\n- Use `productize-completion-status` to log whether the workflow completed, blocked, deferred, or needs review.\n\nTelemetry standard:\n\n- Keep telemetry local by default in `.productize\u002F` or `PRODUCTIZE_STATE_DIR`.\n- Log artifact type, routing decision, evidence gaps, and completion status; do not log secrets or private customer data unless the user explicitly asks for it.\n\nCurrent skill metadata:\n\n- **Skill**: `explore-data`\n- **Lifecycle**: Measure\n- **Category**: Analytics\n- **Primary artifact**: Explore Data analytics diagnosis with metric readout, caveats, decision, and next instrumented step\n\nGenerate a comprehensive data profile for a table or file before deeper analysis.\n\n## Argument Hint\n\n`\u003Ctable or file>`\n\n## Usage\n\n```text\n\u002Fexplore-data \u003Ctable_name or file>\n```\n\n## Workflow\n\n### 1. Access Data\n\nIf a data warehouse or analytics MCP is connected:\n1. Resolve the table name, including schema prefixes.\n2. Query table metadata: columns, types, descriptions, size, update metadata if available.\n3. Run profiling queries against live data. Use sampling for very large tables and disclose it.\n\nIf a file is provided:\n1. Load CSV, Excel, Parquet, or JSON into a working dataset.\n2. Infer column types and normalize obvious parsing issues.\n\nIf neither is available, ask for a table name, file, pasted sample, or schema description. If only a schema is provided, give profiling SQL the user can run.\n\n### 2. Understand Structure\n\nAnswer table-level questions:\n- Rows and columns.\n- Grain: one row per what.\n- Primary key or natural key, and whether it is unique.\n- Last updated timestamp and expected refresh cadence if known.\n- Date coverage and earliest\u002Flatest records.\n\nClassify columns:\n- Identifier: primary keys, foreign keys, entity IDs.\n- Dimension: categorical attributes for grouping\u002Ffiltering.\n- Metric: quantitative values.\n- Temporal: dates and timestamps.\n- Text: free-form strings.\n- Boolean: true\u002Ffalse flags.\n- Structural: JSON, arrays, nested data.\n\n### 3. Profile Columns\n\nTable-level:\n- Total row count.\n- Column count and type breakdown.\n- Approximate table size if available.\n- Date range for temporal columns.\n\nAll columns:\n- Null count and null rate.\n- Distinct count and cardinality ratio.\n- Top 5-10 most common values with frequencies.\n- Rare values when useful for anomaly detection.\n\nNumeric columns:\n- Min, max, mean, median, standard deviation.\n- Percentiles: p1, p5, p25, p75, p95, p99.\n- Zero count and negative count.\n- Distribution shape and outliers.\n\nString columns:\n- Min, max, and average length.\n- Empty string count.\n- Pattern consistency.\n- Case consistency.\n- Leading\u002Ftrailing whitespace.\n\nTemporal columns:\n- Min and max dates.\n- Null and future dates.\n- Distribution by month\u002Fweek.\n- Time series gaps.\n\nBoolean columns:\n- True count, false count, null count, true rate.\n\n### 4. Flag Data Quality Issues\n\nUse severity labels: high, medium, low.\n\nFlag:\n- High null rates: warn above 5 percent, alert above 20 percent.\n- Duplicate natural keys.\n- Low-cardinality IDs or unexpectedly high-cardinality categorical fields.\n- Suspicious values: negative amounts, future dates, placeholders, test values, impossible ranges.\n- Skewed distributions that make averages misleading.\n- Encoding and formatting issues: mixed case, whitespace, inconsistent formats.\n- Cross-column rule violations: completed status with missing completed_at, end date before start date.\n- Staleness or unexpected load lag.\n\n### 5. Discover Patterns\n\nLook for:\n- Foreign key candidates.\n- Natural hierarchies such as country -> state -> city.\n- Numeric correlations worth investigating.\n- Derived columns that appear calculated from other fields.\n- Redundant or near-identical columns.\n- Natural segments based on categorical fields with useful cardinality.\n\n### 6. Recommend What To Analyze Next\n\nSuggest:\n- Best dimensions for slicing data.\n- Key metric columns.\n- Time columns suitable for trends.\n- Natural groupings or hierarchies.\n- Potential join keys.\n- 3-5 concrete follow-up analyses.\n\nExamples:\n- Trend analysis on `[metric]` by `[time_column]` grouped by `[dimension]`.\n- Distribution deep dive on `[skewed_column]`.\n- Data quality investigation on `[problematic_column]`.\n- Correlation analysis between `[metric_a]` and `[metric_b]`.\n- Cohort analysis using `[date_column]` and `[status_column]`.\n\n## Output Format\n\n```markdown\n## Data Profile: [table_or_file]\n\n### Overview\n- Rows:\n- Columns:\n- Grain:\n- Primary key:\n- Date range:\n- Last updated:\n\n### Column Details\n[Summary table grouped by IDs, dimensions, metrics, dates, booleans, text, structural fields]\n\n### Data Quality Issues\n[Severity, field, issue, evidence, recommendation]\n\n### Patterns and Relationships\n[Join keys, hierarchies, correlations, derived\u002Fredundant fields]\n\n### Recommended Explorations\n[Numbered list of follow-up analyses]\n```\n\n## Quality Framework\n\nCompleteness:\n- Complete: more than 99 percent non-null.\n- Mostly complete: 95-99 percent.\n- Incomplete: 80-95 percent.\n- Sparse: below 80 percent.\n\nConsistency checks:\n- Same concept represented multiple ways.\n- Numbers stored as strings.\n- Dates in inconsistent formats.\n- Foreign keys without parents.\n- Business rule violations.\n\nAccuracy red flags:\n- Placeholder values such as 0, -1, 999999, N\u002FA, TBD, test, xxx.\n- Suspicious default values.\n- Stale active-system data.\n- Impossible values.\n- Round-number bias.\n\nTimeliness:\n- Last updated time.\n- Expected update frequency.\n- Event-to-load lag.\n- Gaps in expected time series.\n\n## Schema Documentation Template\n\nWhen documenting the dataset for team use, include:\n- Description.\n- Grain.\n- Primary key.\n- Row count and date.\n- Update frequency.\n- Owner if known.\n- Key columns table.\n- Relationships.\n- Known issues.\n- Common query patterns.\n\n## SQL Discovery Patterns\n\nUse dialect-appropriate schema queries. For PostgreSQL-style systems:\n\n```sql\nSELECT table_name, table_type\nFROM information_schema.tables\nWHERE table_schema = 'public'\nORDER BY table_name;\n\nSELECT column_name, data_type, is_nullable, column_default\nFROM information_schema.columns\nWHERE table_name = 'my_table'\nORDER BY ordinal_position;\n```\n\nFor other warehouses, adapt to the warehouse dialect and metadata tables.\n","\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# Explore Data\n\n## Productize Preamble\n\nBefore producing the artifact, implementation step, or code change, classify the work:\n\n- **User\u002Fpersona**: founder, product leader, AI PM, AI builder, stakeholder, or mixed\u002Funknown.\n- **Product stage**: idea, validation, PMF search, growth, scale, pivot, or unknown.\n- **Artifact mode**: strategy memo, PRD, research plan, positioning, experiment, deck, roadmap, execution brief, diagnostic, or decision record.\n- **Artifact format**: Markdown for short, repo-native, diff-sensitive artifacts; self-contained HTML for long, visual, shareable, interactive, or explicitly requested artifacts.\n- **Evidence standard**: what is known, assumed, missing, and risky.\n- **Decision mode**: recommend, ask for a blocking input, or proceed with explicit assumptions.\n\nOperating rules:\n\n1. Do not produce generic product strategy filler. Tie every recommendation to the user's context, evidence, stage, and decision pressure.\n2. Separate facts from assumptions. Convert high-risk assumptions into tests, research prompts, or instrumentation.\n3. Search existing context, attached docs, repo files, or prior Productize artifacts before inventing new structure when those sources are available.\n4. Ask only for inputs that materially change the output. If the next step is obvious, proceed and state assumptions.\n5. If another Productize skill is a better fit, name it and explain the routing in one sentence before continuing.\n6. Enforce the output contract for this skill. Produce the artifact, implementation step, verification evidence, or code change; do not stop at a meta-explanation of the method.\n7. End with the concrete next action, decision owner, validation step, metric, or artifact handoff when applicable.\n8. Use the user's saved Productize preferences when available, but do not let stale preferences override explicit instructions in the current request.\n9. If you must ask a blocking question, use this compact format: `AskUserQuestion: \u003Cone question> Why it matters: \u003Cdecision it changes>`.\n10. Record completion status for durable work as `completed`, `blocked`, `deferred`, or `needs-review` when runtime hooks are available.\n\nArtifact format policy:\n\n- Default to Markdown for short notes, repo-native documentation, changelog fragments, or artifacts where clean source diffs matter.\n- Use a self-contained HTML file when the user asks for HTML, the artifact is likely to exceed about 100 lines, the reader needs diagrams\u002Ftables\u002Fcomparisons\u002Fscreenshots, the artifact is meant to be shared, or interaction\u002Fexport controls would help the user stay in the loop.\n- Route by product job first, then choose the format. Do not create a generic HTML workflow when a Productize playbook, gate, or routed skill owns the work.\n- HTML artifacts must be local-first and portable: one file, embedded CSS\u002FJS, no remote dependencies unless explicitly requested, readable without a dev server, responsive, accessible, and easy to skim.\n- Prefer semantic sections, tables, SVG diagrams, annotated code blocks, status chips, collapsible detail, and copy\u002Fexport buttons when they improve review speed. Avoid decorative complexity that hides the decision.\n- For implementation work with ambiguities, use `$implementation-notes` when the user asks for a running notes file, especially `implementation-notes.html` or `implementation-notes.md`.\n\nRuntime hooks, if available:\n\n- Use `productize-workflow start \"\u003Cuser request>\"` at the beginning of durable product work; it restores context, routes the request, records the session, and returns the required artifact contract.\n- Use `productize-workflow complete --id \u003Cid> --status completed|blocked|deferred|needs-review --artifact-type \u003Ctype> --summary \u003Csummary>` before ending durable product work; it records the artifact, saves context, and logs completion status.\n- Use `productize-update-check --strict` at the start of maintenance, setup, release, or generated-output work.\n- Use `productize-config` to read or write user\u002Fteam preferences such as persona, artifact mode, evidence threshold, or update-check policy.\n- Use `productize-session-log` to record important workflow decisions.\n- Use `productize-artifact-log` when a durable artifact is produced.\n- Use `productize-context-restore` before restarting long-running product work from scratch.\n- Use `productize-context-save` after producing a durable strategy, research, spec, or stakeholder artifact.\n- Use `productize-registry-search` or `productize-skill-router` when routing is ambiguous.\n- Use `productize-completion-status` to log whether the workflow completed, blocked, deferred, or needs review.\n\nTelemetry standard:\n\n- Keep telemetry local by default in `.productize\u002F` or `PRODUCTIZE_STATE_DIR`.\n- Log artifact type, routing decision, evidence gaps, and completion status; do not log secrets or private customer data unless the user explicitly asks for it.\n\nCurrent skill metadata:\n\n- **Skill**: `explore-data`\n- **Lifecycle**: Measure\n- **Category**: Analytics\n- **Primary artifact**: Explore Data analytics diagnosis with metric readout, caveats, decision, and next instrumented step\n\nGenerate a comprehensive data profile for a table or file before deeper analysis.\n\n## Argument Hint\n\n`\u003Ctable or file>`\n\n## Usage\n\n```text\n\u002Fexplore-data \u003Ctable_name or file>\n```\n\n## Workflow\n\n### 1. Access Data\n\nIf a data warehouse or analytics MCP is connected:\n1. Resolve the table name, including schema prefixes.\n2. Query table metadata: columns, types, descriptions, size, update metadata if available.\n3. Run profiling queries against live data. Use sampling for very large tables and disclose it.\n\nIf a file is provided:\n1. Load CSV, Excel, Parquet, or JSON into a working dataset.\n2. Infer column types and normalize obvious parsing issues.\n\nIf neither is available, ask for a table name, file, pasted sample, or schema description. If only a schema is provided, give profiling SQL the user can run.\n\n### 2. Understand Structure\n\nAnswer table-level questions:\n- Rows and columns.\n- Grain: one row per what.\n- Primary key or natural key, and whether it is unique.\n- Last updated timestamp and expected refresh cadence if known.\n- Date coverage and earliest\u002Flatest records.\n\nClassify columns:\n- Identifier: primary keys, foreign keys, entity IDs.\n- Dimension: categorical attributes for grouping\u002Ffiltering.\n- Metric: quantitative values.\n- Temporal: dates and timestamps.\n- Text: free-form strings.\n- Boolean: true\u002Ffalse flags.\n- Structural: JSON, arrays, nested data.\n\n### 3. Profile Columns\n\nTable-level:\n- Total row count.\n- Column count and type breakdown.\n- Approximate table size if available.\n- Date range for temporal columns.\n\nAll columns:\n- Null count and null rate.\n- Distinct count and cardinality ratio.\n- Top 5-10 most common values with frequencies.\n- Rare values when useful for anomaly detection.\n\nNumeric columns:\n- Min, max, mean, median, standard deviation.\n- Percentiles: p1, p5, p25, p75, p95, p99.\n- Zero count and negative count.\n- Distribution shape and outliers.\n\nString columns:\n- Min, max, and average length.\n- Empty string count.\n- Pattern consistency.\n- Case consistency.\n- Leading\u002Ftrailing whitespace.\n\nTemporal columns:\n- Min and max dates.\n- Null and future dates.\n- Distribution by month\u002Fweek.\n- Time series gaps.\n\nBoolean columns:\n- True count, false count, null count, true rate.\n\n### 4. Flag Data Quality Issues\n\nUse severity labels: high, medium, low.\n\nFlag:\n- High null rates: warn above 5 percent, alert above 20 percent.\n- Duplicate natural keys.\n- Low-cardinality IDs or unexpectedly high-cardinality categorical fields.\n- Suspicious values: negative amounts, future dates, placeholders, test values, impossible ranges.\n- Skewed distributions that make averages misleading.\n- Encoding and formatting issues: mixed case, whitespace, inconsistent formats.\n- Cross-column rule violations: completed status with missing completed_at, end date before start date.\n- Staleness or unexpected load lag.\n\n### 5. Discover Patterns\n\nLook for:\n- Foreign key candidates.\n- Natural hierarchies such as country -> state -> city.\n- Numeric correlations worth investigating.\n- Derived columns that appear calculated from other fields.\n- Redundant or near-identical columns.\n- Natural segments based on categorical fields with useful cardinality.\n\n### 6. Recommend What To Analyze Next\n\nSuggest:\n- Best dimensions for slicing data.\n- Key metric columns.\n- Time columns suitable for trends.\n- Natural groupings or hierarchies.\n- Potential join keys.\n- 3-5 concrete follow-up analyses.\n\nExamples:\n- Trend analysis on `[metric]` by `[time_column]` grouped by `[dimension]`.\n- Distribution deep dive on `[skewed_column]`.\n- Data quality investigation on `[problematic_column]`.\n- Correlation analysis between `[metric_a]` and `[metric_b]`.\n- Cohort analysis using `[date_column]` and `[status_column]`.\n\n## Output Format\n\n```markdown\n## Data Profile: [table_or_file]\n\n### Overview\n- Rows:\n- Columns:\n- Grain:\n- Primary key:\n- Date range:\n- Last updated:\n\n### Column Details\n[Summary table grouped by IDs, dimensions, metrics, dates, booleans, text, structural fields]\n\n### Data Quality Issues\n[Severity, field, issue, evidence, recommendation]\n\n### Patterns and Relationships\n[Join keys, hierarchies, correlations, derived\u002Fredundant fields]\n\n### Recommended Explorations\n[Numbered list of follow-up analyses]\n```\n\n## Quality Framework\n\nCompleteness:\n- Complete: more than 99 percent non-null.\n- Mostly complete: 95-99 percent.\n- Incomplete: 80-95 percent.\n- Sparse: below 80 percent.\n\nConsistency checks:\n- Same concept represented multiple ways.\n- Numbers stored as strings.\n- Dates in inconsistent formats.\n- Foreign keys without parents.\n- Business rule violations.\n\nAccuracy red flags:\n- Placeholder values such as 0, -1, 999999, N\u002FA, TBD, test, xxx.\n- Suspicious default values.\n- Stale active-system data.\n- Impossible values.\n- Round-number bias.\n\nTimeliness:\n- Last updated time.\n- Expected update frequency.\n- Event-to-load lag.\n- Gaps in expected time series.\n\n## Schema Documentation Template\n\nWhen documenting the dataset for team use, include:\n- Description.\n- Grain.\n- Primary key.\n- Row count and date.\n- Update frequency.\n- Owner if known.\n- Key columns table.\n- Relationships.\n- Known issues.\n- Common query patterns.\n\n## SQL Discovery Patterns\n\nUse dialect-appropriate schema queries. For PostgreSQL-style systems:\n\n```sql\nSELECT table_name, table_type\nFROM information_schema.tables\nWHERE table_schema = 'public'\nORDER BY table_name;\n\nSELECT column_name, data_type, is_nullable, column_default\nFROM information_schema.columns\nWHERE table_name = 'my_table'\nORDER BY ordinal_position;\n```\n\nFor other warehouses, adapt to the warehouse dialect and metadata tables.\n",{"name":5,"description":7},"main","f177680a573a242a81bd0a776f9681f620e6d74c","skills\u002Fproductize-explore-data",0,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize","https:\u002F\u002Fgithub.com\u002Fitseffi","2026-08-07 20:07:32",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add itseffi\u002Fproductize --skill productize-explore-data",{"tool":37,"command":38},"bunx","bunx skills add itseffi\u002Fproductize --skill productize-explore-data",{"tool":40,"command":41},"pnpm","pnpm dlx skills add itseffi\u002Fproductize --skill productize-explore-data","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-explore-data\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",325,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-explore-data\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7357QB5M87V95F82E73V2TF","workflow-memory","Maintains workflow-scoped task memory for Productize runs using .productize\u002Ftasks\u002F\u003Cname>\u002Fmemory\u002F files. Use when a task prompt provides workflow memory paths and requires the agent to read, update, compact, and promote durable context across PRD task executions. Do not use for PR review remediation, global user preferences, or programmatic event-log summarization.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-memory\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7357K97HSYEHAQTW5ZKM4CE","review-round","Performs a comprehensive code review of a PRD implementation and generates a review round directory with issue files compatible with fix-reviews. Use when reviewing implemented PRD tasks, creating a manual review round without an external provider, or performing a quality audit of code changes. Do not use for fetching reviews from external providers, fixing existing review issues, executing PRD tasks, or editing source code.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Freview-round\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7357F2NZE5NSYM2SJXEGBFZ","productize","Productize root skill for building, shipping, operating, and growing AI products inside a coding harness. Routes work across thesis framing, discovery, research, positioning, finance, decision making, requirements, design, metrics, AI-builder execution, code implementation, verification, stakeholder narratives, growth, launch, operation, and learning workflows. Use when the user wants to build a product from zero, improve an existing product, or needs product work that spans multiple lifecycle stages before code, launch, operation, or growth execution.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7357B48F8MK86EQF135FJQ6","productize-wwas","Why-What-Acceptance. Use when writing backlog items in Why-What-Acceptance format, breaking features into independent valuable work, or adding strategic context to delivery items.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-wwas\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M735783CDA9MQ0SPR9X6QZSE","productize-writing-plans","Create comprehensive implementation plans with bite-sized tasks. Use when you have requirements before touching code.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-writing-plans\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M735750V5Q6WRBX1ZFGNRMEB","productize-write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea into a structured document, scoping goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into phases.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-write-spec\u002FSKILL.md",[],[]]