satotek.dev valid
satotek.dev
nosuke の個人ブログ・技術メモ。技術・ガジェット・旅行・日常について気ままに書いています。Cloudflare Workers + TanStack Start で構築しています。
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://satotek.dev/llms.txt
- llms-full.txt
- https://satotek.dev/llms-full.txt
- Sections
- 3
- Links
- 12
- Size
- 2181 bytes
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-26T02:21:07.770Z
- Last checked
- 2026-10-26T02:21:08.184Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T02:21:07.778Z. Cached copy · Source on satotek.dev
# satotek.dev
> nosuke の個人ブログ・技術メモ。技術・ガジェット・旅行・日常について気ままに書いています。Cloudflare Workers + TanStack Start で構築しています。
## 主要ページ
- [トップ](https://satotek.dev/): 最新記事の一覧
- [記事一覧](https://satotek.dev/posts): カテゴリ・タグでの絞り込み（技術 / 日常）
- [音楽](https://satotek.dev/music): Last.fm の再生記録
- [プロフィール](https://satotek.dev/profile): 著者紹介・プライバシーポリシー・お問い合わせ
## 記事
- [Pixel 11 で 5G の通信状態を可視化するアプリを作った](https://satotek.dev/posts/cellscope-pixel-5g): Network Signal Guru が使えない Pixel 11 で、接続バンドや CA 構成、電波品質の推移を見るために、Kotlin と Jetpack Compose で CellScope というアプリを作った話。Android からどこまで通信情報が取れるのか、root と priv-app で何が変わるのかも書きます。
- [WebMCP というものを試してみた](https://satotek.dev/posts/webmcp-blog-tools): WebMCP がどんなものなのか確かめるため、satotek.dev で記事の検索・一覧・表示を AI エージェントから試してみた。
- [dotfiles を Nix Flakes で管理している話](https://satotek.dev/posts/nix-flakes-dotfiles): macOS・Linux・WSL・Azure VM の環境を Nix Flakes + Home Manager に寄せた話。設定の書き分け、シェル起動の高速化、AI エージェント設定の宣言管理、flake.lock の自動更新まで。
- [Cloudflare Workers でサイトを作ってみた](https://satotek.dev/posts/cloudflare-workers-site): 普段は Azure を触っている人間が、個人サイトを Cloudflare Workers で立ててみた話。
- [はじめまして](https://satotek.dev/posts/first-post): 自己紹介と、このサイトを作った経緯について。
## 補足
- [全文（LLM向け）](https://satotek.dev/llms-full.txt): 全記事の本文を1ファイルにまとめたもの
- [RSS フィード](https://satotek.dev/feed.xml)
- [サイトマップ](https://satotek.dev/sitemap.xml)
Machine-readable: GET /v1/resolve?q=satotek.dev · GET /v1/domain/satotek.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage satotek.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for satotek.dev:
1. POST https://agentwebmap.com/v1/sites/satotek.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://satotek.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/satotek.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/satotek.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.