Add Emacs as a NinjaClaw communication channel with a local HTTP bridge.
npx skills add https://github.com/OfirGavish/NinjaClaw-Nano --skill add-emacs-ofirgavish
Please help me install this Agent Skill. Skill: add-emacs Source: https://github.com/OfirGavish/NinjaClaw-Nano/tree/main/.copilot/skills/add-emacs Command: npx skills add https://github.com/OfirGavish/NinjaClaw-Nano --skill add-emacs-ofirgavish
Emacs users need a seamless in-editor AI assistant integrated with NinjaClaw. This skill provides a chat buffer, org-mode integration, and a local HTTP bridge so you can talk to NinjaClaw from within Emacs without exposing tokens or relying on external services.
Load NinjaClaw.el in Emacs, configure the bridge, start NinjaClaw, and begin chatting.
High-intent search queries and answers about installing and using this skill.
Emacs integration with NinjaClaw uses a local HTTP bridge on port 8766 and the NinjaClaw.el package to provide an in-editor chat buffer for AI conversations. You load the package, configure the bridge, and start chatting directly from Emacs.
Yes, NinjaClaw Emacs integration works with Doom Emacs, Spacemacs, and vanilla Emacs 27.1 or higher. It provides optional configurations for each distribution to ensure cross-IDE compatibility and one-click setup.
Org-mode integration is enabled by the NinjaClaw.el package to send and receive AI responses directly within Org files. This allows you to interact with NinjaClaw and capture outputs in your org-mode workflow without leaving the editor.
No, you do not need an external service to use AI chat inside Emacs. The integration relies on a local HTTP bridge, ensuring your conversations and tokens remain secure and unexposed to third-party services.
Setup involves loading the NinjaClaw.el package, applying optional Emacs configurations, and starting a local bridge on port 8766. The skill includes environment setup and build instructions to enable in-editor conversations.
The local bridge requires port 8766 to be available and Emacs 27.1 or higher. As a local HTTP bridge, it is designed for in-editor use and does not expose tokens externally, meaning it functions locally rather than as a remote network service.
stevengonsalvezIntegrate Emacs as a NanoClaw channel for in-editor AI chat and org-mode workflows.
plurigridConfigure Emacs with elisp, org, gnus, tramp, and eglot.
nrupalaIntegrate NanoClaw with Emacs via a local HTTP bridge for in-editor AI chat.
thmtzIntegrate Emacs with NanoClaw via a local HTTP bridge for in-editor chat.
