Hono was originally built for Cloudflare Workers and provides first-class support for the entire Cloudflare ecosystem including KV, D1, R2, Durable Objects, Queues, and more.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionhono-cloudflareExecute the skills CLI command in your project's root directory to begin installation:
Fetches hono-cloudflare from bobmatnyc/claude-mpm-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate hono-cloudflare. Access via /hono-cloudflare in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
29
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
29
stars
Hono was originally built for Cloudflare Workers and provides first-class support for the entire Cloudflare ecosystem including KV, D1, R2, Durable Objects, Queues, and more.
Key Features:
Use Hono on Cloudflare when:
npm create hono@latest my-app
# Select: cloudflare-workers
cd my-app
npm install
npm run dev
my-app/
├── src/
│ └── index.ts # Main entry point
├── wrangler.toml # Cloudflare configuration
├── package.json
└── tsconfig.json
// src/index.ts
import { Hono } from 'hono'
const app = new Hono()
app.get('/', (c) => c.text('Hello Cloudflare Workers!'))
export default app
# Deploy to Cloudflare
npx wrangler deploy
# Local development
npx wrangler dev
import { Hono } from 'hono'
// Define your bindings
type Bindings = {
// Environment variables
API_KEY: string
DATABASE_URL: string
// KV Namespaces
MY_KV: KVNamespace
// D1 Databases
DB: D1Database
// R2 Buckets
BUCKET: R2Bucket
// Durable Objects
COUNTER: DurableObjectNamespace
// Queues
MY_QUEUE: Queue
}
const app = new Hono<{ Bindings: Bindings }>()
app.get('/config', (c) => {
// Fully typed access
const apiKey = c.env.API_KEY
return c.json({ configured: !!apiKey })
})
export default app
name = "my-app"
main = "src/index.ts"
compatibility_date = "2024-01-01"
[vars]
API_KEY = "your-api-key" # pragma: allowlist secret
[[kv_namespaces]]
binding = "MY_KV"
id = "your-kv-id"
[[d1_databases]]
binding = "DB"
database_name = "my-database"
database_id = "your-d1-id"
[[r2_buckets]]
binding = "BUCKET"
bucket_name = "my-bucket"
[[queues.producers]]
binding = "MY_QUEUE"
queue = "my-queue"
type Bindings = {
CACHE: KVNamespace
}
const app = new Hono<{ Bindings: Bindings }>()
// Get value
app.get('/cache/:key', async (c) => {
const key = c.req.param('key')
const value = await c.env.CACHE.get(key)
if (!value) {
return c.json({ error: 'Not found' }, 404)
}
return c.json({ key, value })
})
// Get JSON value
app.get('/cache/:key/json', async (c) => {
const key = c.req.param('key')
const value = await c.env.CACHE.get(key, 'json')
return c.json({ key, value })
})
// Set value
app.put('/cache/:key', async (c) => {
const key = c.req.param('key')
const body = await c.req.json()
await c.env.CACHE.put(key, JSON.stringify(body), {
expirationTtl: 3600 // 1 hour
})
return c.json({ success: true })
})
// Delete value
app.delete('/cache/:key', async (c) => {
const key = c.req.param('key')
await c.env.CACHE.delete(key)
return c.json({ success: true })
})
// List keys
app.get('/cache', async (c) => {
const prefix = c.req.query('prefix') || ''
const list = await c.env.CACHE.list({ prefix, limit: 100 })
<Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
bobmatnyc/claude-mpm-skills
bobmatnyc/claude-mpm-skills
bobmatnyc/claude-mpm-skills
bobmatnyc/claude-mpm-skills
bobmatnyc/claude-mpm-skills
bobmatnyc/claude-mpm-skills
hono-cloudflare reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added hono-cloudflare from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
hono-cloudflare is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
hono-cloudflare reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend hono-cloudflare for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend hono-cloudflare for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: hono-cloudflare is the kind of skill you can hand to a new teammate without a long onboarding doc.
hono-cloudflare fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in hono-cloudflare — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
hono-cloudflare is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 37