agentleFS
takeshytakeshy/obsidian-gemini-helper/.agents/skills/add-workflow-node/SKILL.md

add-workflow-node

Skill117 starsChanged 5 months agoMITView on GitHub

Add a new workflow node type to the plugin. Use when implementing a new node type for the workflow engine (e.g., new command, integration, or control flow node).

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. takeshy/obsidian-llm-hub★ 41100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 3 are distinctive, and 13 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 13

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add a new workflow node type called $ARGUMENTS to the plugin.

    line 11
  2. Distinctive:

    Update the following files in order.

    line 15
  3. Very specific:

    Add to WorkflowNodeType union type

    line 18
  4. Very specific:

    Add to WORKFLOW_NODE_TYPES Set (single source of truth for isWorkflowNodeType())

    line 19
  5. Distinctive:

    Add documentation entry for AI workflow generation

    line 23
  6. Very specific:

    Add handle*Node() function with the node's execution logic

    line 26
  7. Very specific:

    Add case in the switch statement to call the handler and log execution

    line 30
  8. Very specific:

    Add to NODE_TYPE_LABELS object (display name)

    line 34
  9. Very specific:

    Add to ADDABLE_NODE_TYPES array

    line 35
  10. Very specific:

    Add to getDefaultProperties() switch (default property values)

    line 36
  11. Very specific:

    Add to getNodeSummary() switch (summary text for node list)

    line 37
  12. Very specific:

    Add to NODE_TYPE_LABELS object

    line 40
  13. Very specific:

    Add case in renderPropertyFields() switch for editor UI fields

    line 41
  14. Distinctive:

    After implementing all changes:

    line 45
  15. Very specific:

    Run npm run lint to check for errors

    line 46
  16. Very specific:

    Run npm run build to verify compilation

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add New Workflow Node Type

Add a new workflow node type called $ARGUMENTS to the plugin.

Required File Changes (ALL must be updated)

Update the following files in order. Missing any file will cause bugs:

1. src/workflow/types.ts

  • Add to WorkflowNodeType union type
  • Add to WORKFLOW_NODE_TYPES Set (single source of truth for isWorkflowNodeType())
  • If forgotten: nodes are skipped during parsing and disappear from visual workflow

2. src/workflow/workflowSpec.ts

  • Add documentation entry for AI workflow generation

3. src/workflow/nodeHandlers.ts

  • Add handle*Node() function with the node's execution logic
  • Export the handler

4. src/workflow/executor.ts

  • Add case in the switch statement to call the handler and log execution
  • If forgotten: node execution fails silently

5. src/ui/components/workflow/WorkflowPanel.tsx

  • Add to NODE_TYPE_LABELS object (display name)
  • Add to ADDABLE_NODE_TYPES array
  • Add to getDefaultProperties() switch (default property values)
  • Add to getNodeSummary() switch (summary text for node list)

6. src/ui/components/workflow/NodeEditorModal.ts

  • Add to NODE_TYPE_LABELS object
  • Add case in renderPropertyFields() switch for editor UI fields

Verification

After implementing all changes:

  1. Run npm run lint to check for errors
  2. Run npm run build to verify compilation
  3. Review each file to ensure the new node type is consistently named

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.