feat(tool): classify Python plugin tools and tool-builfer verify.#293
Merged
Merged
Conversation
Discover python tool file origins and mark project-scoped tools native while user ~/.flocks plugins remain non-native; update tool-builder smoke-test docs. Co-authored-by: Cursor <cursoragent@cursor.com>
Split on-demand skill loading from flocks_skills management, reconcile python plugin source/native flags from disk, move tool-builder validator under scripts/, and update agents, compaction, and tests accordingly. Co-authored-by: Cursor <cursoragent@cursor.com>
…lugin-tool-native-classification Co-authored-by: Cursor <cursoragent@cursor.com> # Conflicts: # flocks/tool/system/skill_load.py
duguwanglong
approved these changes
May 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
discover_python_tool_sources()to map registered Python tool names to their plugin file paths via AST scanning.native=Truefor project-scoped Python tools andnative=Falsefor user~/.flocks/pluginstools based on file origin.tool_search(select:...)plus direct tool invocation instead of inline Python scripts.