Skip to content
Skills Library
Data & analytics · Analysis

forma-graphs-data

/forma-graphs-data

Design knowledge graphs, maps, dashboards, time series and data exploration with verifiable identity, provenance and interaction. Use for relationships and analytical reading; not to turn fictional data or visual position into domain facts.

Repository
forma ↗
Licence
MIT
Last repository change
11.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Design knowledge graphs, maps, dashboards, time series and data exploration with verifiable identity, provenance and interaction. Use for relationships and analytical reading; not to turn fictional data or visual position into domain facts.

Original author description

Design knowledge graphs, maps, dashboards, time series and data exploration with verifiable identity, provenance and interaction. Use for relationships and analytical reading; not to turn fictional data or visual position into domain facts.

How it works

  1. When to use
  2. Inputs
  3. Procedure
  4. Output and stopping condition
  5. Coordination and execution boundaries
Original SKILL.md headings · 44 lines, 445 words
SKILL.md preview
---
name: forma-graphs-data
description: "Design knowledge graphs, maps, dashboards, time series and data exploration with verifiable identity, provenance and interaction. Use for relationships and analytical reading; not to turn fictional data or visual position into domain facts."
metadata:
  version: 1.36.0
---

# Graphs, maps and data

## When to use

- Use for links/backlinks, local/global graphs, canvases, geographic maps, metrics, history and live updates.
- Do not use to infer real relationships from visual proximity or build a dashboard without an analytical question.

This module requires explicit reading; it does not start queries, pipelines or other modules automatically.
Preserve the domain, brand, stack and source of truth; choose a renderer after understanding the data.

For a relevant saved capability, use [reuse by capability](../forma/references/capability-reuse.md): search by the task, not the source project, and bind the mechanism to the destination's own identity and state owners. Read only the matching contract; do not expand a local fix into a redesign. Source names and exact profiles remain provenance or explicit fidelity targets.

## Inputs

- The question the person needs to answer, dataset/source, units, period and expected operation.
- Record identity, relationship/aggregation rules, scale, permissions and examples of known results.

## Procedure

1. Start with a concrete input and result; identify data, derivations and hypotheses.
   Use [playbooks](../forma/references/playbooks.md) to define the deliverable; do not treat fixtures as real metrics.
2. For graphs, read [graphs and knowledge](../forma/references/knowledge-graphs.md).
   Define identity, direction, origin, resolution, counts and rename/delete behavior; separate confirmed relationships, semantic suggestions, clusters and position.
3. For maps/dashboards, read [temporal and geographic data](../forma/references/data-dashboards.md).
   Establish units, denominators, timezone/period, aggregation, scale and stale/no-data states; use [adaptive systems](../forma/references/adaptive-visual-systems.md) only for relevant theme/canvas concerns.
4. Implement filters, selection and inspection while preserving context and making the source accessible.
   Read [interaction and content](../forma/references/interaction-content.md) and, depending on access/update behavior, [contracts and trust](../forma/references/contracts-trust.md). Provide a readable alternative to the canvas.
5. Compare results with known fixtures and perform the rendered task at a representative scale.
   Use [verification](../forma/references/verification.md); check counts, extremes, empty states, keyboard input and applicable update/cancellation behavior.

## Output and stopping condition

Deliver a usable visualization or the requested specification, reading/interaction rules and evidence of the results.
Include only scale, coverage and update limits actually measured, without inventing benchmarks.
Stop when a person can answer the question, inspect the source and obtain the expected result without losing context.
A beautiful graph with incorrect relationships or a rendered map with incorrect totals does not meet acceptance criteria.

## Coordination and execution boundaries

Use Forma Foundations for visual encoding, Forma Interface for controls, and Forma Validation for data and access checks. Trace the data source and relationship semantics before choosing a renderer.
The coordinator selects additional modules; do not recursively dispatch between specialists. Use the available tools according to [capabilities](../forma/references/integrations.md); a tool name does not prove connection or execution.
In-memory examples do not demonstrate persisted updates. Do not add a database, physics simulation, WebGL or geographic service without a concrete need.
Files in this package (2)
  • SKILL.md 4 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · figueirego/forma100MIT
figueirego/forma100MIT

Database snapshot: 13.11.2026 · package version f51147e83aa7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90semantic-web
    Design Semantic Web structures, Ontologies, and Meta-knowledge graphs. Use when: design ontology, semantic web, knowledge graph architecture, rdf data model, sparql, linked data.
  • 100rudder-data-graphs
    Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
  • 100gemini-visualize
    Generates interactive HTML visualizations (concept maps, evidence networks, knowledge graphs) from Gemini analysis results. Use when the user requests a concept map, evidence network, or knowledge graph from completed analysis.
  • 100data-visualization
    Build interactive, accessible charts and dashboards with Recharts, D3, or Victory. Use when "chart", "graph", "data visualization", "analytics dashboard", "metrics display", "time-series", "D3", or "Recharts".
  • 100time-series-decomposer
    Manage time series decomposer operations. Auto-activating skill for Data Analytics. Triggers on: time series decomposer, time series decomposer Part of the Data Analytics skill category. Use when working with time series decomposer functionality. Trigger with phrases like "time…
  • 100ontology-design
    Design formal knowledge models — classes, properties, relationships, hierarchies, and semantic graphs — for knowledge representation and reasoning. Use when the user asks to build an ontology, design a knowledge graph, model entity relationships formally, define class…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.