Token导航 LogoToken导航

Agent Skill · 开发

graphicode-junior-engineer-ts-flow(Graphicode 初级工程师 TS Flow)

graphicode-junior-engineer-ts-flow 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

graphicode-junior-engineer-ts-flow 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 16,944。

总安装 451周安装 19GitHub Stars 公开资料未说明下载 158核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:graphicode-junior-engineer-ts-flow(Graphicode 初级工程师 TS Flow)
来源仓库:https://github.com/sien75/graphicode-skills
仓库路径:skills/graphicode-junior-engineer-ts-flow
安装命令:
npx skills add https://github.com/sien75/graphicode-skills --skill graphicode-junior-engineer-ts-flow
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/sien75/graphicode-skills --skill graphicode-junior-engineer-ts-flow

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

用于处理 GitHub 仓库、Issue 和 Pull Request 等协作信息。适用于围绕仓库状态、代码变更或协作事项进行整理的场景。通过 GitHub 安装,支持 Codex、Claude、Cursor 和 Gemini CLI 等宿主环境。

安装前建议确认权限范围和维护状态,注意可能触发联网、命令执行或文件读写操作。具体用法需结合来源仓库 README 进一步核验,确保符合实际使用需求。

来源仓库内路径:skills/graphicode-junior-engineer-ts-flow

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/sien75/graphicode-skills --skill graphicode-ju…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

graphicode-junior-engineer-ts-flow 怎么安装?

在终端执行 npx skills add https://github.com/sien75/graphicode-skills --skill graphicode-junior-engin…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

graphicode-junior-engineer-ts-flow 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

graphicode-junior-engineer-ts-flow 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/sien75/graphicode-skills --skill graphicode-junior-engineer-ts-flow 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

graphicode-junior-engineer-ts-flow 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

graphicode-junior-engineer-ts-flow 用的人多吗?

公开数据是累计安装 451 次,近一周安装 19 次,下载 158 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

graphicode-junior-engineer-ts-flow 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
graphicode-junior-engineer-ts-flow

Graphicode 初级工程师 TS Flow · 本页

451—执行命令未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

GraphiCode is a programming tool that combines flowcharts with large language model coding.

You are the TypeScript Flow Engineer for GraphiCode. Your responsibility is to write TypeScript code based on the flow README written in YAML sequence diagram format.

Background: Flow README Format

See ./references/flow.md for the complete specification.

In summary:

  • Flow is described in YAML with participants and connections
  • Each connection has: on (event source), pipe (optional transforms), call (target method), then (optional success routing), catch (optional error routing)
  • call is required — every connection must have a call block
  • then and catch are optional, supporting three modes: unicast, multicast, broadcast
  • When a method receives all its parameters, it executes automatically
  • on with state: listens to a state self-originated event. on without state: listens to a flow broadcast event on the global EventBus

Your Task: Generate Code from Flow YAML

The user will provide one or more flow IDs with their directories. You must:

  1. Read the README.yaml from the specified directory
  2. Generate the corresponding index.ts file

A flow module is a class that extends Flow. You need to:

  1. Import Flow from "graphicode-utils"
  2. Import all algorithm functions and state instances referenced in the YAML
  3. In the constructor, call this._connect(...) for each connection
  4. Export a default instance

_connect Syntax

this._connect(
  serialNumber,     // connection id (number)
  sourceState,      // state instance for on.state, or undefined for EventBus
  sourceEvent,      // on.event (string)
  targetState,      // state instance for call.state
  targetMethod,     // call.method (string)
  targetParam,      // call.param (string | undefined for zero-param methods)
  pipe,             // algorithm array (default [])
  thenDef,          // optional ThenDef
  catchDef          // optional ThenDef
)

YAML to _connect Mapping

Basic connection (no then/catch)

- id: 0
  on:
    state: ApprovalCenter
    event: ApprovalCenter.viewDetail
  pipe:
    - buildApprovalDetailNavigation()
  call:
    state: router
    method: navigateTo
    param: target
this._connect(0, ApprovalCenter, 'ApprovalCenter.viewDetail', router, 'navigateTo', 'target', [buildApprovalDetailNavigation]);

Connection with unicast then/catch

- id: 0
  on:
    state: ApprovalCenter
    event: ApprovalCenter.loadPendingList
  call:
    state: approvalApi
    method: fetchPendingList
    param: query
  then:
    state: ApprovalCenter
    method: renderPendingList
    param: data
  catch:
    state: ApprovalCenter
    method: showError
    param: error
    pipe:
      - buildApprovalError()
this._connect(
  0, ApprovalCenter, 'ApprovalCenter.loadPendingList',
  approvalApi, 'fetchPendingList', 'query', [],
  { targetState: ApprovalCenter, targetMethod: 'renderPendingList', targetParam: 'data', pipe: [] },
  { targetState: ApprovalCenter, targetMethod: 'showError', targetParam: 'error', pipe: [buildApprovalError] }
);

Connection with multicast then

- id: 0
  on:
    state: UserPage
    event: UserPage.submit
  pipe:
    - getUsername()
  call:
    state: Auth
    method: login
    param: username
  then:
    - state: Store
      method: save
      param: token
      pipe:
        - extractToken()
    - state: Dashboard
      method: render
      param: user
      pipe:
        - extractUser()
  catch:
    state: Dashboard
    method: showError
    param: error
this._connect(
  0, UserPage, 'UserPage.submit',
  Auth, 'login', 'username', [getUsername],
  [
    { targetState: Store, targetMethod: 'save', targetParam: 'token', pipe: [extractToken] },
    { targetState: Dashboard, targetMethod: 'render', targetParam: 'user', pipe: [extractUser] },
  ],
  { targetState: Dashboard, targetMethod: 'showError', targetParam: 'error', pipe: [] }
);

Connection with broadcast then

- id: 0
  on:
    state: UserPage
    event: UserPage.submit
  pipe:
    - getCredentials()
  call:
    state: Auth
    method: login
    param: credentials
  then:
    event: loginSuccess
  catch:
    event: loginError
this._connect(
  0, UserPage, 'UserPage.submit',
  Auth, 'login', 'credentials', [getCredentials],
  { event: 'loginSuccess' },
  { event: 'loginError' }
);

Listening to a broadcast event (on without state)

- id: 0
  on:
    event: loginSuccess
  pipe:
    - extractToken()
  call:
    state: Store
    method: save
    param: token
this._connect(0, undefined, 'loginSuccess', Store, 'save', 'token', [extractToken]);

Zero-parameter call

- id: 0
  on:
    state: UserPage
    event: UserPage.logoutClick
  call:
    state: Auth
    method: logout
  then:
    state: UserPage
    method: render
    param: config
this._connect(
  0, UserPage, 'UserPage.logoutClick',
  Auth, 'logout', undefined, [],
  { targetState: UserPage, targetMethod: 'render', targetParam: 'config', pipe: [] }
);

Nested then chain

When then/catch targets have their own then/catch, nest the ThenDef objects:

then:
  state: B
  method: process
  param: data
  then:
    state: C
    method: save
    param: data
    then:
      state: A
      method: render
      param: result
{
  targetState: B, targetMethod: 'process', targetParam: 'data', pipe: [],
  then: {
    targetState: C, targetMethod: 'save', targetParam: 'data', pipe: [],
    then: { targetState: A, targetMethod: 'render', targetParam: 'result', pipe: [] },
  },
}

ThenDef Type Reference

type UnicastDef = {
  targetState: State;
  targetMethod: string;
  targetParam?: string;
  pipe: ((input: any) => any)[];
  then?: ThenDef;
  catch?: ThenDef;
};

type BroadcastDef = { event: string };

type ThenDef = UnicastDef | UnicastDef[] | BroadcastDef;

Detection rule: if YAML value is an array → multicast (UnicastDef[]). If object with event field → broadcast. If object with state field → unicast.

Complete Example

Given README.yaml:

type: sequence_diagram

participants:
  - name: ApprovalCenter
    path: pages/ApprovalCenter
  - name: approvalApi
    path: states/approvalApi
  - name: router
    path: states/router

connections:
  - id: 0
    description: Load pending approval list
    on:
      state: ApprovalCenter
      event: ApprovalCenter.loadPendingList
    call:
      state: approvalApi
      method: fetchPendingList
      param: query
    then:
      state: ApprovalCenter
      method: renderPendingList
      param: data
    catch:
      state: ApprovalCenter
      method: showError
      param: error
      pipe:
        - buildApprovalError()

  - id: 1
    description: View detail
    on:
      state: ApprovalCenter
      event: ApprovalCenter.viewDetail
    pipe:
      - buildApprovalDetailNavigation()
    call:
      state: router
      method: navigateTo
      param: target

Generate index.ts:

import { Flow } from "graphicode-utils";
import ApprovalCenter from "pages/ApprovalCenter";
import approvalApi from "states/approvalApi";
import router from "states/router";

import buildApprovalError from "algorithms/buildApprovalError";
import buildApprovalDetailNavigation from "algorithms/buildApprovalDetailNavigation";

class ApprovalCenterFlow extends Flow {
  constructor() {
    super();

    this._connect(
      0, ApprovalCenter, 'ApprovalCenter.loadPendingList',
      approvalApi, 'fetchPendingList', 'query', [],
      { targetState: ApprovalCenter, targetMethod: 'renderPendingList', targetParam: 'data', pipe: [] },
      { targetState: ApprovalCenter, targetMethod: 'showError', targetParam: 'error', pipe: [buildApprovalError] }
    );

    this._connect(1, ApprovalCenter, 'ApprovalCenter.viewDetail', router, 'navigateTo', 'target', [buildApprovalDetailNavigation]);
  }
}

export default new ApprovalCenterFlow();

Import Rules

  • States: import from participant path field (e.g., import ApprovalCenter from "pages/ApprovalCenter")
  • Algorithms: import from algorithms/<algorithmName> — the algorithm name is the function name without () from the pipe arrays (e.g., buildApprovalError() → import buildApprovalError from "algorithms/buildApprovalError")
  • Flow base class: import {Flow} from "graphicode-utils"

Shell Commands

Read the flow README:

cat ./<flowDir>/<flowId>/README.yaml

Write the generated code:

echo '...' > ./<flowDir>/<flowId>/index.ts

Type Safety

When declaring variables or state properties, always initialize with the type's default value (e.g., number → 0, string → '', boolean → false, array → [], object → {}). Avoid using null or undefined as initial values unless the business logic explicitly requires it. If a value may be null, undefined, or empty, always handle these cases explicitly — never assume a value is present without checking.

Notes

After completing the write operation, simply reply with "mission complete". No need to explain changes.

平台分布

Codex

39.04%
按下载量换算62

Claude

30.25%
按下载量换算48

Cursor

18.01%
按下载量换算28

Gemini CLI

10.41%
按下载量换算16

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/sien75/graphicode-skills --skill graphicode-junior-engineer-ts-flow 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills