<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tools on it-learn.io | IT, Networking &amp; Cybersecurity Blog</title><link>https://blog.it-learn.io/tags/tools/</link><description>Recent content in Tools on it-learn.io | IT, Networking &amp; Cybersecurity Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.it-learn.io/tags/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>The SE's Toolkit: Scripts, Templates, and Resources I Use Every Week</title><link>https://blog.it-learn.io/posts/2026-05-14-se-toolkit-scripts-templates-resources/</link><pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate><guid>https://blog.it-learn.io/posts/2026-05-14-se-toolkit-scripts-templates-resources/</guid><description>&lt;p&gt;Every Solutions Engineer develops a personal toolkit over time — the templates, scripts, cheat sheets, and frameworks that make the difference between a productive week and a chaotic one. The problem is that most of this toolkit lives in scattered documents, random folders, and the SE&amp;rsquo;s memory. When you need the discovery call template, it is in a Google Doc you shared with a colleague two years ago. When you need the subnet calculator, you Google it fresh every time. When you need the competitive battle card, you remember the key points but cannot find the document.&lt;/p&gt;</description></item></channel></rss>