一键在 Manus 中运行任何 Skill

docker-workflow

星标0

分支0

更新时间2026年7月1日 15:15

Docker commands and rules for materials-kg. Use when running the app, testing in containers, or rebuilding after code changes.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

Bobr2610

Bobr2610/materials-kg

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Docker Workflow

Quick Start

# Start everything (Neo4j + API)
docker compose up -d

# Check status
docker compose ps

# View logs
docker compose logs -f materials-api

# Stop
docker compose down

Rebuild After Code Changes

docker compose up -d --build

Services

Service	URL	Container
API	http://localhost:8090	materials-kg-api
Neo4j Browser	http://localhost:7474	materials-kg-neo4j

One-Off Commands

# Run tests in container
docker compose exec materials-api python -m pytest kg_engine/tests/ -v

# Run linter in container
docker compose exec materials-api ruff check kg_engine/

# Open Python shell
docker compose exec materials-api python

Environment Setup

# Copy and edit .env
cp .env.example .env

# Required vars:
# NEO4J_USER=neo4j
# NEO4J_PASSWORD=changeme
# OPENROUTER_API_KEY=your_key

Rules

ALWAYS prefer Docker over running Python directly
NEVER hardcode Neo4j credentials — use .env
After code changes → docker compose up -d --build
Check logs before claiming something works or doesn't
Never commit .env — only .env.example

同仓库更多 Skills

同仓库

code-style

Bobr2610/materials-kg

Python code style and knowledge graph conventions for materials-kg. Use when writing or reviewing Python code.

2026-07-010

mimo-subagent

Bobr2610/materials-kg

Reusable MiMo CLI orchestration skill for delegating work to MiMo across any project. Use this skill whenever the user asks to use mimo, MiMo CLI, mimo run, mimo-auto, MiMo as a subagent, an external autonomous agent, or wants a task delegated to MiMo for research, coding, or summarization. Prefer this skill even when the user does not explicitly mention a skill but clearly wants work routed through MiMo.

2026-07-010

critical-thinking

Bobr2610/materials-kg

Anti-yes-man rules. Use before writing code, reviewing proposals, or responding to user suggestions.

2026-07-010

team-coordination

Bobr2610/materials-kg

Team workflow rules. Use at conversation start to check TEAM_STATUS.md, ask user role, and prevent duplicate work.

2026-07-010

materials-knowledge-graph

Bobr2610/materials-kg

Use for materials science knowledge graph tasks — extracting entities, building graph, querying by material/mode/property, finding data gaps, or any task involving the kg_engine/ module. Triggers on materials science queries, alloy/property extraction, graph construction, gap analysis, or hybrid search.

2026-07-010

name	docker-workflow
description	Docker commands and rules for materials-kg. Use when running the app, testing in containers, or rebuilding after code changes.

Docker Workflow

Quick Start

# Start everything (Neo4j + API)
docker compose up -d

# Check status
docker compose ps

# View logs
docker compose logs -f materials-api

# Stop
docker compose down

Rebuild After Code Changes

docker compose up -d --build

Services

Service	URL	Container
API	http://localhost:8090	materials-kg-api
Neo4j Browser	http://localhost:7474	materials-kg-neo4j

One-Off Commands

# Run tests in container
docker compose exec materials-api python -m pytest kg_engine/tests/ -v

# Run linter in container
docker compose exec materials-api ruff check kg_engine/

# Open Python shell
docker compose exec materials-api python

Environment Setup

# Copy and edit .env
cp .env.example .env

# Required vars:
# NEO4J_USER=neo4j
# NEO4J_PASSWORD=changeme
# OPENROUTER_API_KEY=your_key

Rules

ALWAYS prefer Docker over running Python directly
NEVER hardcode Neo4j credentials — use .env
After code changes → docker compose up -d --build
Check logs before claiming something works or doesn't
Never commit .env — only .env.example