My Blog

Tag: GitHub

  • AI Tools: Anthropic’s Engineers Stopped Building AI Agents. Here’s What They Build Instead.

    Watch on YouTube: https://www.youtube.com/watch?v=VxGIopUQVKo

    Channel: Sharbel A.

    Introduction

    The video from Sharbel A. explains why Anthropic’s engineers shifted from building a separate AI agent for every task to creating reusable “skills.” A skill is a lightweight, self‑contained unit that can be installed once and used repeatedly, much like an app on a smartphone. This approach reduces the overhead of maintaining many half‑trained agents and lets a single agent gain many capabilities through a library of skills.

    What the video covers

    The presentation walks through the concept of a skill, shows how to create one using three different methods, and explains how to share or discover existing skills in community marketplaces. It also highlights the mechanics of progressive disclosure, the structure of the skill.md file, and practical safety tips for installing third‑party skills.

    Step‑by‑step walkthrough of creating a skill

    • Define the task – Identify a repetitive job you want your AI agent to perform (e.g., searching a niche on VidIQ, formatting a report, or launching a specific workflow).
    • Create the skill folder – Make a new directory on your local machine; inside it place a file named skill.md.
    • Write the skill metadata – At the top of skill.md add a name and a description. The description tells the agent when the skill should be activated (think of it as a trigger phrase or condition).
    • Add step‑by‑step instructions – Below the metadata, list the exact actions the agent must take to complete the task. Use clear, imperative language so the agent can follow each step without ambiguity.
    • Save and test – Save the file, then point your agent at the folder. The agent will first read only the name and description; if those match the current context, it will load the full skill and execute the instructions.
    • Refine – Run the skill a few times, observe any mismatches, and adjust the description or instructions until the agent reliably triggers and completes the task.

    Three creation methods demonstrated

    • Manual authoring – You write the skill.md file yourself, following the structure above.
    • Claude‑guided generation – In the Claude UI, use the “create with Claude” option: describe the job in natural language, let Claude draft a skill, then edit the generated skill.md for accuracy.
    • Screen recording – Record yourself performing the task, upload the recording to Claude, and ask it to learn the steps. Claude will produce a skill that mirrors the recorded workflow.

    Tools and numbers mentioned

    • Claude – the underlying AI model used to create and run skills.
    • VidIQ – example tool referenced in a prompt (“YouTube pockets”).
    • Hermes, Codex, Cursor, Permees – additional tools cited as examples of what skills might interact with.
    • Cloud (marketplace), Skills MP, Lobe Hub, GitHub – platforms where existing skills can be found or shared.
    • Find Skills skill – a helper skill for discovering other skills.
    • Agent Hermes’ Mission Control – an example of a skill that orchestrates multiple actions.
    • skill.md – the core file that defines a skill.
    • Plus sign (UI element) – the button used to add a new skill in the Claude interface.

    Caveats and hype check

    The video frames the skill concept as a productivity improvement, not as a revenue‑generating scheme. It avoids making explicit earnings promises, affiliate promotions, or unverified claims. The tone remains educational and tool‑focused. A practical warning is included: always read the entire skill description and scan it for potentially malicious content before installing any third‑party skill.

    Concrete next actions

    • Identify a repetitive task you currently perform with your AI agent and draft a skill.md file for it (include name, description, and step‑by‑step instructions).
    • Try creating a skill manually using the Claude UI to become familiar with the folder and file structure.
    • Use Claude’s “create with Claude” feature: describe the job, let Claude generate a draft skill, then refine the skill.md file.
    • Record a screen walkthrough of a task, have Claude learn from the recording, and export the resulting skill for reuse.
    • Search the Claude skills explorer, GitHub, Skills MP, or Lobe Hub for existing skills that match your needs, then import them into your agent.
    • Before installing any third‑party skill, review its description and instructions for signs of unwanted or harmful behavior.
    • Share your own skill by exporting the folder containing skill.md and distributing the file or a download link to teammates or the community.

  • Grok Bot: I Gave GrokBot Claude Code, Codex, and Grok Build

    Watch on YouTube: https://www.youtube.com/watch?v=8dxzMgr2tow

    Channel: Kacper Rutkiewicz | AI Made Simple

    Introduction

    The video demonstrates how to run external command‑line interfaces—Claude Code, Codex, and Grok Build—inside a GrokBot instance. It shows that GrokBot works as a relay, forwarding prompts to the CLIs while drawing on the user’s own API subscriptions, and it walks through a live build of a simple one‑page website for a fictional cleaning company.

    What the video covers

    The presenter explains the installation process for each CLI, how to authenticate them with personal Claude, OpenAI, and xAI accounts, and why explicit commands such as “use Claude Code” are required to avoid GrokBot attempting the task itself and consuming its weekly limit. A practical example is built step by step: a cleaning‑company landing page is created, validated with Codex, and enhanced with a price calculator using Grok Build. The video also shows how to clone a personal GitHub repository via GrokBot for remote access and how to set up a webhook that lets Claude Code delegate research tasks to GrokBot, returning results as HTML.

    Step‑by‑step walkthrough

    • Install the Claude Code, Codex, and Grok Build CLIs on the GrokBot environment following the login prompts shown in the video.
    • Authenticate each CLI with the corresponding personal subscription (Claude for Claude Code, OpenAI for Codex, xAI for Grok Build) so the tools use your own API limits.
    • When prompting GrokBot, prepend the request with the explicit tool name—for example, “use Claude Code: create a landing page for a cleaning company”—to ensure the CLI, not GrokBot, performs the work.
    • Use Claude Code to generate the initial HTML and CSS for a one‑page site that includes a header, service list, booking form, and contact section.
    • Run Codex on the generated code to identify and fix three booking‑related issues, such as missing form action attributes and validation gaps.
    • Employ Grok Build to add a functional price calculator that instantly quotes services based on vehicle size (e.g., SUV) and selected extras like pet hair removal.
    • Clone your own GitHub repository (the “Deep Rooted AI OS” example) through GrokBot, enabling you to pull code and run commands from a mobile device.
    • Configure a webhook URL in GrokBot so that Claude Code can send research prompts to it; GrokBot processes the request and returns the result as HTML snippets.
    • Monitor the usage dashboards for Claude, OpenAI, and xAI separately; observe that GrokBot’s weekly consumption remains low because most token usage is offloaded to the external CLIs.
    • Join the presenter’s free “AI Made Simple” community to access a detailed step‑by‑step guide and ask follow‑up questions.

    Tools and numbers mentioned

    • Subscription costs referenced: $200 per month for certain plans, $209 for another option.
    • Plan names: Ultra plan, Super Grok plan, Cursor Pro Plus, Cursor Ultra.
    • Usage percentages: 43% and 44% (illustrating GrokBot’s minimal change when CLIs are used).
    • Time estimates: 8‑10 minutes to complete the demo build.
    • Design detail: 44‑pixel spacing mentioned in the layout.
    • Specific features: free quote request form, SUV vehicle option, pet hair removal add‑on.
    • Model/reference: Opus 5.5 (cited in the context of the demo).
    • Low‑usage figure: 1% (indicating GrokBot’s own consumption when external CLIs handle the workload).

    Caveats and hype check

    The video emphasizes that GrokBot’s weekly usage barely changes when the external CLIs are employed, suggesting a potential reduction in GrokBot‑specific consumption. However, the actual savings depend on individual usage patterns, the specific plans you hold, and how frequently you invoke each tool. The presenter’s claim that “you only need one subscription to get started” refers to the ability to authenticate each CLI with the service you already pay for, but you still need separate accounts for Claude, OpenAI, and xAI to use their respective CLIs. The video also promotes the creator’s free community and guide; viewers should evaluate whether those resources match their learning preferences.

    Concrete next actions

    • Follow the installation steps shown in the video to add Claude Code, Codex, and Grok Build to your GrokBot instance.
    • Log in to each CLI with your personal Claude, OpenAI, and xAI credentials so the tools draw on your own API limits.
    • Always prefix GrokBot prompts with the explicit tool name (e.g., “use Codex:”) to prevent GrokBot from attempting the task and using its weekly quota.
    • Build a simple one‑page site for a service business, then run Codex to catch and fix any form‑handling bugs.
    • Enhance the site with Grok Build by adding a calculator that quotes prices based on vehicle size and optional extras.
    • Clone a personal GitHub repository via GrokBot to enable remote code access from a phone or tablet.
    • Set up a webhook in GrokBot that allows Claude Code to send research tasks and receive HTML‑formatted results.
    • Track your Claude, OpenAI, and xAI usage separately in their respective dashboards to confirm that GrokBot’s own consumption stays low.
    • Sign up for the free “AI Made Simple” community to obtain the detailed walkthrough guide and ask questions about the setup.