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
llms-full.txt: https://www.milesker.xyz/llms-full.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

  • New Features
    • Added a new website entry for Milesker with comprehensive metadata, descriptive content sections, and associated reference links. The new listing is now integrated into the platform, providing users with an additional website resource to explore and access within the content collection alongside existing entries.

@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:25pm

@coderabbitai
Copy link

coderabbitai bot commented Nov 17, 2025

Walkthrough

A new MDX data file is added to the content websites directory containing metadata and descriptive information for Milesker. The file defines configuration fields within YAML front matter followed by markdown content sections. No functional logic or code is introduced.

Changes

Cohort / File(s) Summary
New content data file
packages/content/data/websites/milesker-llms-txt.mdx
Adds new MDX file with YAML front matter defining website metadata (name, description, website URL, category, publish date) and markdown body content

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Simple static data file addition with no logic, tests, or dependencies to verify
  • YAML front matter and content structure consistency can be spot-checked against existing similar files in the directory

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 'feat: add Milesker to llms.txt hub' directly and clearly describes the main change: adding a new website entry (Milesker) to the llms.txt hub content collection.
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-1763410894964

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 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 a30d70e.

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

Based on the context gathered from Linear, I now have sufficient information to provide a concise summary relevant to this PR review.

Relevant Context for PR #462 Review

Project Status and Pattern The PR targets the llms.txt hub project, which is currently "In Progress" and led by David Dias. This is an active, ongoing initiative to curate a collection of websites offering llms.txt files.

Similar Submission Pattern Recent related issues show that adding entries to the hub follows a standard submission workflow:

  • Issue THE-1133: "Add vercel llms.txt" (completed)
  • Issue THE-1134: "Add upsun.com" (pending)

These issues demonstrate that submissions are tracked individually and processed as discrete additions to the hub.

Data Structure Context

The submission follows the established pattern seen in similar entries, utilizing MDX files with YAML front matter containing:

  • Metadata fields (name, description, website, llmsUrl, llmsFullUrl, category, publishedAt)
  • Markdown body content

Submission Details to Verify During Review

Review Recommendations

Focus the review on:

  1. Verifying the provided URLs are accessible and valid
  2. Confirming YAML metadata completeness and correctness
  3. Ensuring the file follows existing naming conventions (milesker-llms-txt.mdx)
  4. Validating that the agency-services category is appropriately assigned,,
⏰ 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 (1)
packages/content/data/websites/milesker-llms-txt.mdx (1)

1-13: Confirm the file naming and data structure align with existing hub conventions.

The submission follows a logical structure with complete metadata and matching description text. To ensure consistency, please verify that:

  1. The filename milesker-llms-txt.mdx follows the project's naming convention for other entries
  2. The YAML metadata fields and their format match existing entries in the hub
  3. The category agency-services is a valid/recognized category in the hub

You can verify this by examining a few existing entries in the packages/content/data/websites/ directory to confirm the naming pattern, metadata structure, and valid categories used.

Comment on lines +1 to +9
---
name: 'Milesker'
description: 'Milesker. is a strategy and innovation studio designing imaginative strategies and brand ecosystems for lasting impact, led by founder Romain Lartigue in Paris.'
website: 'https://www.milesker.xyz/'
llmsUrl: 'https://www.milesker.xyz/llms.txt'
llmsFullUrl: 'https://www.milesker.xyz/llms-full.txt'
category: 'agency-services'
publishedAt: '2025-11-17'
---
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify the provided URLs are accessible and contain valid llms.txt content.

The YAML front matter is well-formed with all required metadata fields present. However, the core value of this submission depends on verifying that the URLs are accessible and the llms.txt endpoints contain valid content.

Please run the following script to verify the URLs are accessible and the llms.txt files exist:


🏁 Script executed:

#!/bin/bash
# Description: Verify that all provided URLs are accessible and llms.txt endpoints contain content

# Website URL
echo "=== Checking website URL ==="
curl -s -I https://www.milesker.xyz/ | head -1

# llms.txt endpoint
echo -e "\n=== Checking llms.txt endpoint ==="
curl -s -I https://www.milesker.xyz/llms.txt | head -1
curl -s -w "\nContent length: %{size_download} bytes\n" https://www.milesker.xyz/llms.txt | head -20

# llms-full.txt endpoint
echo -e "\n=== Checking llms-full.txt endpoint ==="
curl -s -I https://www.milesker.xyz/llms-full.txt | head -1
curl -s -w "\nContent length: %{size_download} bytes\n" https://www.milesker.xyz/llms-full.txt | head -20

Length of output: 1481


Need to verify the redirect destination and check for the existence of llms files elsewhere on the domain:


🏁 Script executed:

#!/bin/bash
# Check redirect destination and follow chain
echo "=== Following llms.txt redirect ==="
curl -s -L -w "\nFinal URL: %{url_effective}\nStatus: %{http_code}\n" https://www.milesker.xyz/llms.txt | head -30

echo -e "\n=== Checking common llms file locations ==="
for path in /llms.txt /llms-full.txt /public/llms.txt /public/llms-full.txt /content/llms.txt /.well-known/llms.txt; do
  status=$(curl -s -o /dev/null -w "%{http_code}" https://www.milesker.xyz$path)
  echo "GET $path: HTTP $status"
done

Length of output: 2887


Remove or correct the non-existent llmsFullUrl endpoint.

The llms.txt endpoint works correctly after following its 301 redirect and returns valid content. However, llmsFullUrl at line 6 points to a non-existent endpoint (HTTP 404 across all attempted paths). Either remove this field if the file doesn't exist, or provide the correct URL to the full llms file.

The submission cannot be accepted with a broken URL reference in the metadata.

🤖 Prompt for AI Agents
In packages/content/data/websites/milesker-llms-txt.mdx around lines 1 to 9, the
llmsFullUrl field (line 6) points to a non-existent endpoint returning 404;
either remove the llmsFullUrl line entirely if there is no full file, or replace
its value with the correct working URL to the full LLMS file, then verify the
new URL returns HTTP 200 (or follow redirects) before committing.

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