10-ai-agent-rules
- **Direct and technical:** Be direct and technical in responses — no conversational filler ("Great", "Certainly", "Okay", "Sure") - **One tool at a time:** Wait for user confirmation after each tool use before proceeding - **Verify before completing:** Check task requirements, verify output files e…
Install / Use
npx skills add Themis128/cloudless.grInstalls into whichever agent you are using.
.clinerules
Cline rules
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of 10-ai-agent-rules
10-ai-agent-rules scores 51/100 on our quality scale, 4247th of 4,611 Development & Engineering skills we index.
Its .clinerules is 2.2 KB long, split into 7 sections and no code examples: moderately detailed.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- Our last check on 2026-10-18 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
10-ai-agent-rules compared with similar skills
All 4 of these similar skills score higher than 10-ai-agent-rules; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| 10-ai-agent-rules (this skill)by Themis128 | 51 | 0 | — | .clinerules |
| taste-skillby Leonxlnx | 100 | 110.8k | 1d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 69.9k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 46.6k | 2d ago | CLAUDE.md |
| algorithmic-artby anthropics | 100 | 177.9k | 44d ago | SKILL.md |
Frequently asked questions
- How do I install 10-ai-agent-rules?
- Run
npx skills add Themis128/cloudless.gr. The install tabs above show the steps for each supported agent. - Which AI agents does 10-ai-agent-rules work with?
- It is written for Cline, as a .clinerules file. Other agents that read the same format can often use it too.
- Is 10-ai-agent-rules safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is 10-ai-agent-rules still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubAI Agent Rules
General Behavior
- Direct and technical: Be direct and technical in responses — no conversational filler ("Great", "Certainly", "Okay", "Sure")
- One tool at a time: Wait for user confirmation after each tool use before proceeding
- Verify before completing: Check task requirements, verify output files exist, confirm format constraints before using
attempt_completion - No trailing questions: Never end
attempt_completionwith a question or request for further conversation
Code Changes
- Default to replace_in_file: For most changes, use targeted edits
- Use write_to_file for: New files, extensive changes, boilerplate generation
- Consider context: Ensure changes are compatible with existing codebase and follow project standards
- Fix tests: If existing tests fail after a change, fix the code — don't modify test assertions unless explicitly asked
Problem Solving
- Break down tasks: Set clear, achievable goals and work through them sequentially
- Use sequential thinking: For complex problems, use the Sequential Thinking MCP server
- Gather context first: Read relevant files before making changes
- Check environment: Consider actively running terminals, project structure, and system information
Security
- No AWS CLI installation: Never install AWS CLI on developer machines, Pi hosts, or CI agents
- No new AWS SDK: Don't add AWS SDK dependencies to new code — prefer Cloudflare-native solutions
- Secret management: Use Wrangler secrets for Workers, environment variables for k3s
- SSM_DISABLED=1: ETL scripts set this to bypass SSM — use D1 app_config or env vars instead
Skills Usage
- Match to task: When a user's request matches a skill description, use
use_skillto load it - Follow skill instructions: After activation, follow the skill's instructions directly
- Available skills: Refer to the system prompt for the full list of available skills
MCP Tool Usage
- One MCP operation at a time: Similar to other tools, wait for confirmation before proceeding
- Resolve before query: For Context7, call
resolve-library-idbeforequery-docs - Check server status: Use
test-mcp-servers.shif MCP servers are unresponsive
Related Skills
taste-skill
110.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
69.9kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
46.6kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.