Omni Apps introduces a new AI agent skill called brain-link-discipline. This tool addresses a common frustration for developers and teams: receiving a link to a page that doesn't work or isn't immediately available. It fundamentally changes how links to your content are handled, ensuring a functional link is delivered without delay.
This skill makes sure that every time you create, edit, or report a page, a WORKING link ships in the same message rather than as a follow-up. Its core purpose is to eliminate the back-and-forth of asking for a page link, only to find it's broken or not yet reflecting the latest changes. It streamlines collaboration by providing immediate, reliable access to your work.
Ensuring Valid Links from the Start
When you create, edit, or report a page, brain-link-discipline takes responsibility for delivering a functional URL immediately. The traditional workflow often involves a delay between a page update and its accessible link, or even worse, sending a link that leads to a 404 error. This tool prevents those scenarios. It's designed to ensure that the link provided in your chat message is not just a placeholder but a direct path to the current, accessible version of your content.
This immediate delivery of a working link saves time and reduces friction in communication. There's no need for manual checks or subsequent messages to confirm if a link is live. brain-link-discipline integrates this validation directly into the process, so you can trust the link you receive or send.
Mechanical Path Derivation and Verification
The tool derives paths mechanically by using git ls-files --full-name. This approach is reliable because it directly queries the repository's file structure, bypassing assumptions about server configurations or custom routing. Crucially, before any link is sent in a chat message, brain-link-discipline first pushes any pending changes to the remote repository. This pre-emptive action ensures that the content the link points to is the absolute latest version available, preventing situations where a link is sent to an outdated page.
Following the push, the tool then verifies that the generated link resolves successfully. This verification step is not just about formatting; it's a live check to confirm the URL leads to an accessible resource, minimizing the chance of sending a broken reference. For example, imagine you've just finished editing a new section in docs/user-guide/advanced-features.md. You then ask the AI agent for a link to this updated page. brain-link-discipline will ensure that your local changes to advanced-features.md are pushed to your remote Git repository, and then it will test if the corresponding web URL, perhaps yourdomain.com/docs/user-guide/advanced-features, is live and responding before delivering that link to you. This systematic process prevents situations where you send a link only to find out moments later that it points to an outdated version or a non-existent page.
Robust Fallback Mechanisms
In scenarios where a hosted remote is not available or an absolute URL cannot be verified, brain-link-discipline does not simply fail. Instead, it employs robust fallback mechanisms. It will first attempt to provide repo-relative paths. For instance, if an absolute URL cannot be confirmed, it might give you path/to/your-document.md. This is particularly useful for collaborators who have local access to the repository and can navigate directly to the file within their local environment.
If neither a hosted remote nor a straightforward repo-relative path is suitable or verifiable, the tool can then generate a shareable HTML artifact using the publish command. This ensures that even in complex or unhosted environments, a concrete, accessible version of the page can always be provided. These fallbacks mean that regardless of your repository's hosting situation, you can reliably get a working reference to your content.
Context-Aware Link Handling and Triggers
It's important to distinguish how brain-link-discipline handles links based on context. Links embedded within pages themselves remain relative. This design choice is deliberate; it helps preserve the backlink graph within your documentation and ensures portability of your content. This means your internal cross-references won't break if your base URL changes or if content is moved within the repository. However, when the tool communicates links in chat messages, it consistently uses verified absolute URLs. This distinction ensures maximum utility and reliability for different use cases – maintaining internal structure while providing direct, verifiable external access.
brain-link-discipline responds to several explicit and implicit triggers. You can activate it by simply saying 'give me the link' or 'where is the page' in your chat. It also steps in automatically when it detects a link 404 error in communication, during bulk page reports, or as part of subagent relays, providing the correct, working link. It's important to note its defined boundaries: this skill is not for fixing broken citations inside existing pages. Similarly, publishing artifacts more broadly or routing work to subagents are separate skills, each handled by specialized agents within the Omni Apps ecosystem.
Frequently Asked Questions
Q1: What happens if the link verification fails?
If brain-link-discipline cannot verify an absolute URL – perhaps due to temporary network issues, a misconfigured host, or if no hosted remote is configured – it does not simply fail. Instead, it systematically falls back to alternative methods to provide a working reference. It will first attempt to provide a repo-relative path, such as path/to/document.md. If neither an absolute nor a repo-relative path is suitable or verifiable, the tool can then generate a shareable HTML artifact using the publish command. This ensures that a concrete, accessible version of the page is always provided.
Q2: Can I use this for internal links within my documentation?
No, links inside pages remain relative. This skill's primary function is to ensure that chat messages contain verified absolute URLs when you request or refer to a page. It maintains the integrity of your internal backlink graph by not altering relative links within the page content itself.
Q3: Is it possible to use brain-link-discipline to fix all broken links on my site?
No, this skill is not designed for fixing broken citations within existing pages. Its purpose is to ensure that when a new or updated page is referenced in chat, a working link is provided immediately. Tools for auditing and fixing existing broken links are separate functions.
Implementing brain-link-discipline streamlines how you share and access page content. It makes sure that when a link is sent, it just works, every time.
