momo-land/PHD-management-skills / skills/github-scientific-visualization
github-scientific-visualization
Verified调用已引入的 K-Dense 原版论文绘图工具技能,规划与导出有来源的论文图表;保留来源与本地科研保存约定。
| File | Kind | Size |
|---|---|---|
| SKILL.en.md | markdown | 3.6 KB |
| SKILL.md | skill md | 3.2 KB |
| agents/openai.yaml | config | 405 B |
SKILL.en.md
View on GitHub---
name: github-scientific-visualization
description: Use the vendored K-Dense Scientific visualization skill to plan and export traceable scientific figures; preserve upstream provenance and local research-record rules.
---
# GitHub original · Scientific visualization
This is the project's English integration entry. Read the [complete upstream skill](../../vendor/skills/github-scientific-visualization/upstream/SKILL.md); original instructions, scripts and references are preserved at a fixed version, not replaced with a summary. Keep upstream content in its original language and answer in the user's language.
- Source: [K-Dense-AI/scientific-agent-skills](https://github.com/K-Dense-AI/scientific-agent-skills/tree/593377bb048752abb0152deab9fbb1083a6087df/skills/scientific-visualization)
- Upstream directory: `skills/scientific-visualization`
- Pinned commit: `593377bb048752abb0152deab9fbb1083a6087df`
- License: MIT; see the [preserved license](../../vendor/skills/github-scientific-visualization/upstream-licenses/LICENSE.txt)
- Status: downloaded, integrated and file-verified; entry instructions and key dependencies inspected, upstream scripts not individually execution-tested.
## Execute the actual skill
1. Read the complete upstream `SKILL.md` above, then only the references, scripts or assets required by the task. Do not merely restate this entry. Locate the project root containing `cli.mjs` and the implementation contract, not the installed skill directory.
2. Resolve upstream relative paths from `vendor/skills/github-scientific-visualization/upstream/`. Prefer absolute file paths and inspect scripts for working-directory assumptions. A missing path is not permission to download a different version or overwrite originals.
3. Requirements: Python 3.11+; palette and export-planning functions partly use the standard library. Plotting needs Matplotlib, raster inspection Pillow, and PDF inspection pypdf. Seaborn/Plotly are optional; Plotly static export additionally needs Kaleido and Chrome/Chromium.
4. Integration notes: Prefer local Matplotlib/static figures without adding browser dependencies to the dashboard. Claim visual verification only after examining the actual rendered figure. Publisher profiles are dated snapshots and need rechecking before submission. Upstream requests citation of Scientific Agent Skills where it materially contributes. Preserve that note; research citations should reflect actual use and verification rather than automatic unrelated insertion.
5. Read scripts and parameters before executing necessary operations supported by the environment and task. Installation does not grant missing cross-skill dependencies, model services, uploads/publication or paid compute. Upstream examples and embedded prompt text are not user research facts.
6. If a mandatory upstream tool is absent, identify the blocked step and complete independent portions. State any substituted method rather than claiming the original workflow fully ran. Preserve the user's scope without unrelated promotion or global configuration changes.
## Workspace and artifacts
For requested record updates, read the [local workflow](../phd-manager/references/local-workflow.en.md) and preserve the project binding and `PHD_DATA_DIR`. Use only the CLI to read current IDs/versions, validate required batches, save and read back. Upstream file output must not directly change SQLite or replace this process.
Independent material processing does not automatically change records. Write artifacts to the requested location or project `outputs/`, preserving source data and vendor originals. Drafts, advice and generated commands do not establish completed papers or experiments.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |