Skip to content

Conversation

@thedaviddias
Copy link
Owner

@thedaviddias thedaviddias commented Nov 17, 2025

This PR adds Milesker to the llms.txt hub.

Submitted by: romain.lartigue

Website: https://www.milesker.xyz/
llms.txt: https://www.milesker.xyz/llms.txt

Category: agency-services


This PR was created via admin token for a user without GitHub repository access.

Please review and merge if appropriate.

Summary by CodeRabbit

  • Documentation
    • Added new website content entry for Milesker with comprehensive metadata including name, description, website and LLMs URLs, category classification, and publication date. The entry is now available in the content library alongside other website resources. All Milesker resource information is fully accessible through the library system for end-users.

@vercel
Copy link

vercel bot commented Nov 17, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
llms-txt-hub Ready Ready Preview Comment Nov 17, 2025 8:48pm

@coderabbitai
Copy link

coderabbitai bot commented Nov 17, 2025

Walkthrough

A new MDX content file is added to document the Milesker LLMs resource within the website content directory. The file contains metadata in YAML frontmatter and a simple description body with no functional code changes.

Changes

Cohort / File(s) Change Summary
New content file
packages/content/data/websites/milesker-llms-txt.mdx
New MDX file added with YAML frontmatter (name, description, website, llmsUrl, llmsFullUrl, category, publishedAt) and descriptive body content for Milesker LLMs resource.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

  • Simple static content addition with no logic or structural implications
  • Standard frontmatter structure consistent with existing content files
  • No external dependencies or functional changes to validate

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely summarizes the main change: adding Milesker to the llms.txt hub, which directly matches the file addition and PR objectives.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch submit-milesker-1763412346515

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 935e684 and 42316e8.

📒 Files selected for processing (1)
  • packages/content/data/websites/milesker-llms-txt.mdx (1 hunks)
🧰 Additional context used
🔍 Remote MCP

I'll search for relevant information to help with the pull request review. Let me verify key details about the submission.## Summary of Relevant Context for PR Review

Company Verification

Milesker drives bold innovation and strategic transformation, empowering brands to thrive tomorrow, elevating brand value and customer experience while unlocking new digital and business opportunities for lasting impact. Romain Lartigue is the founder of Milesker, with 25 years of experience in brand building and digital transformation. This confirms the submitter and company legitimacy.

llms.txt Hub Context

The llms.txt file is a standardized way to provide information about how LLM-powered tools and services should interact with your documentation and codebase, and this repository serves as a central hub for discovering and sharing llms.txt implementations across different projects and platforms. The hub organizes projects into primary categories (AI & ML, Developer Tools, Data & Analytics, Integration & Automation, Infrastructure & Cloud, Security & Identity) and secondary categories (personal, agency, e-commerce, education, media, international, other).

Category Appropriateness

The PR's categorization as "agency-services" aligns with the hub's documented secondary categories, which includes "agency" as a valid classification for service-oriented businesses like Milesker.

Technical Validation Notes

llms.txt curates a list of real URLs, and the content has to exist – and deliver – when the model gets there. This means the reviewer should verify that the llms.txt file actually exists at the provided URL (https://www.milesker.xyz/llms.txt) and contains valid, accessible content.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Validate
🔇 Additional comments (3)
packages/content/data/websites/milesker-llms-txt.mdx (3)

2-3: Inconsistent product name: verify "Milesker" vs "Milesker." formatting.

The name field uses "Milesker" (no period), but the description consistently refers to "Milesker." (with period). Confirm this is intentional and consistent with how the company brand itself presents their name.


1-13: Metadata structure and consistency look good.

The YAML frontmatter is well-structured with all expected fields, the category "agency-services" is appropriate per the hub's taxonomy, and the published date aligns with the PR submission. The body content duplicates the frontmatter description, maintaining consistency.


5-6: No issues found. The configuration is correct as-is.

The llmsUrl is valid and accessible—it returns HTTP 200 after following a standard 301 redirect managed by Squarespace. The content is well-structured with meaningful studio information, expertise guidelines, and AI instructions.

The empty llmsFullUrl field is appropriate because llms-full.txt does not exist on this domain (both the standard and trailing-slash variants return HTTP 404). Since the extended variant is optional and unavailable, leaving the field empty is the correct approach.


Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants