A crowdsourced collection of tools to empower Large Language Models in Emacs.

• Installation
• Usage
• Tool List
  • Filesystem
  • Buffers
  • Search
  • System
• Contributing
  • Faster Iteration

Quick and dirty: clone the repository and add it to load-path.

(add-to-list 'load-path "/path/to/llm-tool-collection/")
(require 'llm-tool-collection)

;; For gptel:
(mapcar (apply-partially #'apply #'gptel-make-tool)
        (llm-tool-collection-get-all))

;; For llm:
(mapcar (apply-partially #'apply #'llm-make-tool)
        (llm-tool-collection-get-all))

Every tool is defined with a symbol llm-tc/tool-name that has both a variable value and a function value. The variable value contains the tool specification, which can be passed to any compliant Emacs LLM client. The function value contains the function that runs the given tool. This can be instrumented or run manually.

To register just one tool:

;; For gptel:
(apply #'gptel-make-tool llm-tc/list-directory)

;; For llm:
(apply #'llm-make-tool llm-tc/list-directory)

Use llm-tool-collection-get-category to map over a list of tools pertaining to a specific task.

;; For gptel:
(mapcar (apply-partially #'apply #'gptel-make-tool)
        (llm-tool-collection-get-category "filesystem"))

;; For llm:
(mapcar (apply-partially #'apply #'llm-make-tool)
        (llm-tool-collection-get-category "filesystem"))

Use llm-tool-collection-get-tag to map over a list of tools with a specific tag.

;; For gptel:
(mapcar (apply-partially #'apply #'gptel-make-tool)
        (llm-tool-collection-get-tag 'editing))

;; For llm:
(mapcar (apply-partially #'apply #'llm-make-tool)
        (llm-tool-collection-get-tag 'editing))

See Tool List for a list of tool names, descriptions, and categories.

Author

@skissue

Tags

filesystem, editing

Allows the LLM to open a file and read its contents.

Author

@skissue

Tags

filesystem

Allows the LLM to list the contents of a directory.

Author

@skissue

Tags

filesystem, editing

Allows the LLM to create a new file with specified content. Returns an error if the file already exists.

Author

@skissue

Tags

filesystem

Allows the LLM to create a new directory. Returns an error if the directory already exists.

Author

@ultronozm

Tags

filesystem, editing, introspection

Views the contents of a file. Optional offset and limit let you show a slice of lines.

Author

@ultronozm

Tags

filesystem, editing

Replaces **exactly one** occurrence of a string in a file with a new string.

Author

@ultronozm

Tags

filesystem, search

Expands a Unix‑style glob pattern (e.g. *.el) and returns the matching paths.

Author

@ultronozm

Tags

filesystem, editing

Completely overwrites a file with the supplied content.

Author

@ultronozm

Tags

filesystem

Lists directory contents, with optional regexps to ignore.

Author

@ultronozm

Tags

buffers, editing, introspection

Allows the LLM to view the contents of a buffer. The LLM can optionally specify a line offset to start from, as well as a limit on the number of lines to return.

Author

@ultronozm

Tags

buffers, editing

Replaces **exactly one** occurrence of a string in a buffer.

Author

@ultronozm

Tags

buffers, editing

Overwrites an entire buffer with new content.

Author

@ultronozm

Tags

buffers, search, introspection

Regex search inside a buffer; returns matching line numbers plus text.

Author

@ultronozm

Tags

buffers, introspection

Lists user‑relevant buffers, excluding internal/temp buffers.

Author

@ultronozm

Tags

filesystem, search, system

Recursive grep -E with line numbers. Supports include glob and path root.

Author

@ultronozm

Tags

system, execution

Runs an arbitrary Bash command and returns its standard output (errors if exit is nonzero).

To write a new tool, use the llm-tool-collection-deftool macro. For details on its usage, see its docstring as well as the existing tools.

(llm-tool-collection-deftool read-file ; Tool name
  ;; Specs
  (:category "filesystem" :tags (filesystem editing) :confirm t :include t)
  ;; Arguments, with LLM-friendly documentation and types
  ((path "Path to the file to read. Supports relative paths and '~'."
         :type string))
  ;; LLM-friendly tool documentation
  "Read the contents of a file and return its content as a string."
  ;; Implementation body
  (with-temp-buffer
    (insert-file-contents (expand-file-name path))
    (buffer-string)))

It’s highly recommended to include :tags, as well as appropriate values for the :confirm and :include parameters, depending on how dangerous the tool may be. Additionally, docstrings should be as LLM-friendly; consider instructing models on when to call a tool, and what tools it may want to chain together.

After defining a tool, make sure to add it to the README! Use the existing documentation structure as an example.

For non-trivial/complex tools, it’s recommended to include a short screencast or demo of the tool in action. If able to test, also consider adding a note on which models tend to perform the best with the tool.

When ready, submit a PR!

(defun llm-tool-collection-register-with-gptel (tool-spec)
  "Register a tool defined by TOOL-SPEC with gptel.
TOOL-SPEC is a plist that can be passed to `gptel-make-tool'."
  (apply #'gptel-make-tool tool-spec))

(add-hook 'llm-tool-collection-post-define-functions
          #'llm-tool-collection-register-with-gptel)