一键导入
chart-best-practices
Best practices for creating effective data visualizations with create_chart tool
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Best practices for creating effective data visualizations with create_chart tool
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | chart-best-practices |
| description | Best practices for creating effective data visualizations with create_chart tool |
| maturity | mature |
| tags | ["visualization","charts","data-presentation","best-practices","feishu","vchart"] |
| triggers | [{"when_user_mentions":["chart","charts","graph","visualize","visualization","图表","可视化","数据可视化","画图","绘图"]},{"when_tool_is_called":"create_chart"}] |
| version | 1.0.0 |
Guide for creating clear, effective chart visualizations using the create_chart tool.
The chart renderer auto-detects field mappings based on field names. Use descriptive field names instead of generic x/y:
[
{ "week": "周一", "steps": 8500 },
{ "week": "周二", "steps": 12000 }
]
[
{ "x": "周一", "y": 8500 },
{ "x": "周二", "y": 12000 }
]
line) - Trends Over TimeBest for: Showing changes over continuous time periods
{
"chartType": "line",
"title": "📈 周度步数统计",
"data": [
{ "week": "周一", "steps": 8500 },
{ "week": "周二", "steps": 12000 },
{ "week": "周三", "steps": 7800 }
],
"aspectRatio": "2:1"
}
Data format: [{ time_field: string, value_field: number }]
bar) - ComparisonsBest for: Comparing values across discrete categories
{
"chartType": "bar",
"title": "🏆 销售排行榜",
"data": [
{ "product": "iPhone", "sales": 4500 },
{ "product": "MacBook", "sales": 3200 },
{ "product": "iPad", "sales": 2800 }
],
"aspectRatio": "16:9"
}
Data format: [{ category_field: string, value_field: number }]
pie) - ProportionsBest for: Showing parts of a whole (≤ 6 categories)
{
"chartType": "pie",
"title": "💰 本月支出分布",
"data": [
{ "name": "房贷", "value": 12000 },
{ "name": "餐饮", "value": 3500 },
{ "name": "交通", "value": 800 }
],
"aspectRatio": "1:1"
}
Data format: [{ name: string, value: number }]
linearProgress) - Progress TrackingBest for: Showing completion percentage
{
"chartType": "linearProgress",
"title": "🎯 年度储蓄目标",
"data": [
{ "value": 42, "total": 50 }
]
}
Data format: [{ value: number, total: number }]
circularProgress) - Circular ProgressBest for: Circular progress indicators
{
"chartType": "circularProgress",
"title": "🎯 项目进度",
"data": [
{ "type": "总进度", "value": 0.15, "text": "15%" }
]
}
Data format: [{ type: string, value: number (0-1), text?: string }]
IMPORTANT:
value should be normalized between 0-1 (e.g., 0.15 = 15%)type is required for category/labeltext is optional for display textscatter) - CorrelationsBest for: Showing relationships between two variables
{
"chartType": "scatter",
"title": "📈 身高体重关系",
"data": [
{ "height": 170, "weight": 65 },
{ "height": 175, "weight": 70 }
]
}
Data format: [{ x_field: number, y_field: number }]
The renderer recognizes these patterns for auto-detection:
X-Axis / Category fields:
week, day, month, year, time, datecategory, label, name, typeY-Axis / Value fields:
value, count, amount, sales, stepsscore, total, number1:1 - Square, best for mobile and pie charts2:1 - Wide, good for line/bar charts (default)4:3 - Standard, balanced for most charts16:9 - Widescreen, best for PC/dashboardbrand - Default Feishu theme (recommended)rainbow - Vibrant multi-color (good for pie charts)complementary - Two complementary colorsprimary - Single color gradientspecUse the spec parameter for fine-grained control:
{
"chartType": "bar",
"data": [...],
"spec": {
"legends": { "visible": true, "orient": "bottom" },
"axes": [
{ "orient": "bottom", "title": { "text": "月份" } },
{ "orient": "left", "title": { "text": "销售额" } }
]
}
}
Limit data points:
Use clear titles:
"📈 销售趋势""2024年Q1营收" not "数据"Choose appropriate aspect ratio:
1:1 or 2:116:9 for longer trendsAvoid chart spam:
❌ Too many pie slices:
// Bad: 10 categories in pie chart
{ "chartType": "pie", "data": [ ...10 items... ] }
✅ Use bar chart instead:
{ "chartType": "bar", "data": [ ...10 items... ] }
❌ Missing descriptive fields:
// Bad: Generic field names
{ "chartType": "bar", "data": [{ "x": "A", "y": 10 }] }
✅ Use meaningful names:
{ "chartType": "bar", "data": [{ "product": "iPhone", "sales": 10 }] }
{
"chartType": "pie",
"title": "💰 月度支出",
"data": [
{ "name": "房租", "value": 8000 },
{ "name": "餐饮", "value": 3000 },
{ "name": "交通", "value": 500 }
],
"aspectRatio": "1:1",
"colorTheme": "rainbow"
}
{
"chartType": "line",
"title": "🏃 本周步数",
"data": [
{ "day": "周一", "steps": 8500 },
{ "day": "周二", "steps": 12000 },
{ "day": "周三", "steps": 7800 }
],
"aspectRatio": "16:9"
}
{
"chartType": "bar",
"title": "🏆 销售排行 TOP 5",
"data": [
{ "name": "张三", "sales": 50000 },
{ "name": "李四", "sales": 45000 },
{ "name": "王五", "sales": 38000 }
],
"aspectRatio": "4:3",
"colorTheme": "brand"
}
skills/feishu/feishu-card-charts.mdCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
The Baidu Baike Component is a knowledge service tool designed to query authoritative encyclopedia explanations for various nouns. Its core function is given a specific "noun" (object, person, location, concept, event, etc.) provided by the user, it returns a standardized, detailed entry explanation sourced from Baidu Baike.
Baidu Scholar Search - Search Chinese and English academic literature (journals, conferences, papers, etc.)
Search the web using Baidu AI Search Engine (BDSE). Use for live information, documentation, or research topics.
模拟顶级对冲基金投研决策流程,为股票制定机构级交易策略备忘录。 使用此技能当用户需要: - 进行股票深度分析 - 制定交易策略 - 撰写投研报告或投资备忘录 - 进行多空辩论分析 - 评估投资风险回报比 触发词:股票分析、投研报告、投资备忘录、hedge fund、股票研究、交易策略、基本面分析、技术分析、估值分析
Beeclaw's dynamic preference learning system. This skill automatically detects and learns user preferences from conversation patterns. TRIGGER when user expresses format preferences ("don't use emoji", "be concise"), identifies their role ("I'm a frontend engineer"), gives feedback on output style, or establishes habits/rituals. Preferences are stored in facts/preferences.md and applied to all future interactions.