Skip to main content
Manusで任意のスキルを実行
ワンクリックで
GitHub リポジトリ

yamlgraph

yamlgraph には sheikkinen から収集した 7 個の skills があり、リポジトリ単位の職業カバレッジとサイト内 skill 詳細ページを表示します。

収集済み skills
7
Stars
3
更新
2026-06-28
Forks
0
職業カバレッジ
4 件の職業カテゴリ · 100% 分類済み
リポジトリエクスプローラー

このリポジトリの skills

author-prompt
ソフトウェア開発者

Author YAMLGraph prompt YAML files. Use when: writing prompt templates, configuring inline schemas or output_schema, using Jinja2 templates, adding system/user messages, defining structured output fields, or using system_segments for prompt caching.

2026-06-28
author-graph
ソフトウェア開発者

Author YAMLGraph graph YAML files. Use when: creating or editing graph YAML, adding nodes or edges, configuring routing and conditions, setting up state keys, variables, data_files, tools, loop limits, error handling, or verification gates.

2026-05-22
chaplain-ops
ネットワーク・コンピュータシステム管理者

Operate the Chaplain automation system. Use when: starting the chaplain, checking pipeline status, submitting proposals to inbox, debugging pipeline failures, retrying failed topics, cleaning worktrees, running the philosopher or inquisitor.

2026-05-22
feature-request
プロジェクト管理専門家

Create and manage YAMLGraph feature requests. Use when: writing a feature request, planning a feature, following the plan-judge-enforce workflow, submitting a proposal to the chaplain inbox, understanding the FR lifecycle, or writing acceptance criteria.

2026-05-22
release-version
ソフトウェア開発者

Release a new YAMLGraph version. Use when: bumping version, creating a release, tagging, pushing a release, freezing changelog, or handling pre-commit hook cascades during release.

2026-05-22
run-code-analysis
ソフトウェア品質保証アナリスト・テスター

Run code quality analysis on YAMLGraph. Use when: running ruff, bandit, radon, vulture, pytest coverage, checking code quality, finding dead code, security scanning, or generating improvement recommendations. For autonomous analysis, use the code-analysis agent instead.

2026-05-22
check-langsmith-trace
ソフトウェア品質保証アナリスト・テスター

Check LangSmith traces for YAMLGraph runs. Use when: debugging graph execution, reviewing LLM latency or token usage, investigating failed runs, verifying tracing config, querying recent traces, troubleshooting LangSmith connectivity.

2026-05-22