Skip to main content
ZICQ

Skills ZICQ category:Writing & Research daily-coding

Daily Coding

Use for everyday coding tasks that involve writing or modifying source code.

339 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Use for everyday coding tasks that involve writing or modifying source code.

When to use it

Use this skill for:

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Daily Coding Checklist; When to Use; When Not to Use; Core Checklist; Before Starting; During Coding.

File analysis

File analysis: instruction-only skill (SKILL.md). The agent loads the full body when activated.

Daily Coding ChecklistWhen to UseWhen Not to UseCore ChecklistBefore StartingDuring CodingAfter CompletionQuick ReferenceCommon Mistakes to Avoid❌ Don't✅ Should❌ Don't

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
daily-coding
description
Use for everyday coding tasks that involve writing or modifying source code.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "daily-coding" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-8ec68d373f561f4f-Daily-Coding.html
Save it as .cursor/skills/daily-coding/SKILL.md or .claude/skills/daily-coding/SKILL.md and keep the frontmatter name and description exactly as-is.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/galaxy-dawn/claude-scholar' --list

npx skills add 'https://github.com/galaxy-dawn/claude-scholar' --skill 'daily-coding'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout

name: daily-coding description: Use for everyday coding tasks that involve writing or modifying source code. version: 1.0.0 tags: [Coding, Daily, Checklist]

Daily Coding Checklist

A minimal coding quality assurance checklist ensuring every code modification follows best practices.

When to Use

Use this skill for:

  • Implementing new features
  • Adding code or modifying existing code
  • User requests like "write a...", "implement...", "add...", or "modify..."
  • Any coding task that involves Edit or Write tools

When Not to Use

Do not use this skill for:

  • Pure reading or understanding tasks with no modification intent
  • Work already covered by specialized skills such as bug-detective, architecture-design, or verification-loop
  • Configuration-only changes
  • Documentation-only writing

Core Checklist

Before Starting

  • [ ] Read before modify - Must read target file with Read tool before making changes
  • [ ] Understand context - Confirm understanding of existing code logic and design intent

During Coding

  • [ ] Minimal changes - Only change what's necessary, no over-engineering, no unrelated features
  • [ ] Type safety - Add type hints for Python, avoid any in TypeScript
  • [ ] Security check - Avoid command injection, XSS, SQL injection vulnerabilities

After Completion

  • [ ] Verify execution - Ensure code runs correctly with no syntax errors
  • [ ] Clean up - Remove print/console.log debug statements and temporary files
  • [ ] Brief summary - Inform user what was changed and the scope of impact

Quick Reference

Common Mistakes to Avoid

# ❌ Don't
def process(data=[]):  # Mutable default argument
    pass

# ✅ Should
def process(data: list | None = None):
    data = data or []
# ❌ Don't
except:  # Bare except
    pass

# ✅ Should
except ValueError as e:
    logger.error(f"Processing failed: {e}")
    raise

Security Check Points

  • User input must be validated/escaped
  • Use pathlib for file paths, avoid path traversal
  • Never hardcode sensitive info (API keys, passwords)

Related skills

Writing & Research

Humanizer

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on…

Writing & Research

Prismfy Search

Default web search for OpenClaw. Search the web across 10 engines — Google, Reddit, GitHub, arXiv, Hacker News, and more — using Prismfy. Fr…

Writing & Research

Blogwatcher

Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.

Writing & Research

Tavily

AI-optimized web search using Tavily Search API. Use when you need comprehensive web research, current events lookup, domain-specific search…