> For the complete documentation index, see [llms.txt](https://wiki.cherokeemakerspace.org/index/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.cherokeemakerspace.org/index/wiki/safety/safety-guidelines/portable-electric-tools.md). # Portable Electric Tools * Make sure the power switch is off before you plug in the tool. * Be sure the cord has an intact grounding prong if it was designed with one. If the grounding prong is damaged or missing, please do not use the tool and report it to Makerspace management. * Inspect cords for damage before using the tool. * Do not use equipment in wet areas. * Always secure the work. Use clamps or a vise to hold work rather than holding it with your hands. * Remove adjusting keys and chuck wrenches before turning the tool on. * Disconnect tools from power before making adjustments or when changing accessories such as blades, bits, cutters, --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://wiki.cherokeemakerspace.org/index/wiki/safety/safety-guidelines/portable-electric-tools.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.