<Devsly/>
NotebookLM Watermark Remover
Remove the NotebookLM watermark from PDF slide exports — free, unlimited, and 100% in your browser.
View
NotebookLM Video Watermark Remover
Remove the NotebookLM watermark from every frame of your MP4 and auto-trim the end card — free and unlimited.
View
Gemini Watermark Remover
Remove the Gemini (Veo) sparkle watermark from every frame of your AI-generated MP4 — free and unlimited.
View
MCP https://devsly.io/mcp MCP Tools Best Skills API Docs

Keyboard Shortcuts

Navigation

Quick Search
⌘ / Ctrl + K
Toggle Dark Mode
⌘ / Ctrl + D
Close Dialogs
Esc

Tool Actions

Execute / Process
⌘ / Ctrl + Enter
Clear Input
⌘ / Ctrl + Shift + C
Copy Output
⌘ / Ctrl + Shift + X

Editor

Select All
⌘ / Ctrl + A
Undo
⌘ / Ctrl + Z
Redo
⌘ / Ctrl + Shift + Z

Updated 2w ago

by ilang-ai

autocode

You say it. AutoCode ships it. 48 skills. Code to deployment in one session. iLang v5.0 judgment + secret-safe deploys. Free forever.

Works with
  • Claude
View on GitHub (opens in a new tab)

107 GitHub stars (107)

+4 in 30 days

Stars gained per day · daily snapshots since Sep 26
Stars gained per day, Sep 26 to Nov 5: +4 in total; the busiest day was Sep 29 with +1 stars.Sep 27: 0 starsSep 28: 0 starsSep 29: +1 starsSep 30: −1 starsOct 1: 0 starsOct 2: 0 starsOct 3: 0 starsOct 4: 0 starsOct 5: 0 starsOct 6: 0 starsOct 7: 0 starsOct 8: 0 starsOct 9: 0 starsOct 10: 0 starsOct 11: 0 starsOct 12: 0 starsOct 13: 0 starsOct 14: 0 starsOct 15: 0 starsOct 16: 0 starsOct 17: 0 starsOct 18: +1 starsOct 19: 0 starsOct 20: 0 starsOct 21: 0 starsOct 22: 0 starsOct 23: 0 starsOct 24: 0 starsOct 25: 0 starsOct 26: 0 starsOct 27: 0 starsOct 28: +1 starsOct 29: +1 starsOct 30: 0 starsOct 31: 0 starsNov 1: 0 starsNov 2: +1 starsNov 3: 0 starsNov 4: 0 starsNov 5: 0 stars
Stars gained between daily snapshots
PeriodNew stars
Sep 270
Sep 280
Sep 29+1
Sep 30−1
Oct 10
Oct 20
Oct 30
Oct 40
Oct 50
Oct 60
Oct 70
Oct 80
Oct 90
Oct 100
Oct 110
Oct 120
Oct 130
Oct 140
Oct 150
Oct 160
Oct 170
Oct 18+1
Oct 190
Oct 200
Oct 210
Oct 220
Oct 230
Oct 240
Oct 250
Oct 260
Oct 270
Oct 28+1
Oct 29+1
Oct 300
Oct 310
Nov 10
Nov 2+1
Nov 30
Nov 40
Nov 50
  • 11 skills (11 skills found in its SKILL.md files)
  • 22 forks (22 forks)
  • 2w ago last update (Last updated 2w ago)

Install

Skills CLI

npx skills add ilang-ai/autocode

Asks which skills and agents to install. Just one: npx skills add ilang-ai/autocode --skill build — add -g for every project.

Claude Code

git clone https://github.com/ilang-ai/autocodecp -r "autocode/skills/build" ~/.claude/skills/

Copies the build skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.

Plugin

/plugin marketplace add ilang-ai/autocode

Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.

Skills can run code on your machine — read the SKILL.md first.

What it does

In the author's own words, from each skill's SKILL.md.

  • build

    S4 of see-it-ship-it: build one feature at a time, simplest stack that works, checkpoint before anything risky, rules kept apart from the look so they can be verified without a browser, learned numbers tagged. Includes first-session environment setup and running where you build.

    skills/build/SKILL.md on GitHub (opens in a new tab)
  • fix

    Cross-cutting: when something breaks. Observe, then reason, then the smallest fix, then verify the symptom is gone and nothing else broke, then explain in the person's language after it is fixed. Never show a raw error to a beginner; never blame them.

    skills/fix/SKILL.md on GitHub (opens in a new tab)
  • hand-back

    S7 of see-it-ship-it: what the person hears. Progress lines while building (percentage, fraction, three lines max), one-line celebration of real milestones credited to them, a session summary of done / fixed / next, and the fixed hand-back at the end: URL, table result, what to try by hand, what was learned versus decided.

    skills/hand-back/SKILL.md on GitHub (opens in a new tab)
  • judge

    The judgment layer: when AutoCode acts on its own and when it stops and asks, and how it speaks about decisions and money. iLang v5.0: perception sets the 11 dimensions, the frozen reference function f_v5 sets the mode, the user sees one plain line. Runs before every consequential action.

    skills/judge/SKILL.md on GitHub (opens in a new tab)
  • memory

    Cross-cutting: what AutoCode remembers and how every session starts. Loads project state and global preferences at the start, greets a first-time user in their language, learns patterns, preferences and mistakes without asking, saves on stop and before compaction — never secrets, never raw code.

    skills/memory/SKILL.md on GitHub (opens in a new tab)
  • plan

    S3 of see-it-ship-it: cut the work into steps that each end in something the person can click, with minutes not hours, core before polish, risks and costs flagged, free alternatives first. Internal planning is written in iLang; the person never sees it.

    skills/plan/SKILL.md on GitHub (opens in a new tab)
  • product-study

    Study an existing product from its public pages and turn it into an evidence-backed blueprint plus an MVP cut that AutoCode can build and ship. Use this whenever the user wants something "like X", "similar to X", "my own version of X", "a clone of X", names a competitor they admire, or pastes a product URL and asks to build it — even when they never say "research" or "analyze". Public sources onl…

    skills/product-study/SKILL.md on GitHub (opens in a new tab)
  • security

    Auto-apply security basics and block deploys that would leak secrets. Never ask the user about security choices — just do it, and run a real secret scan before going live.

    skills/security/SKILL.md on GitHub (opens in a new tab)
  • see

    S1 of see-it-ship-it: understand what the person wants from the way they said it. Classify intent silently, detect their level from the first messages, size the task, lock what they confirmed, and ask at most one question that is theirs to answer.

    skills/see/SKILL.md on GitHub (opens in a new tab)
  • ship

    S6 of see-it-ship-it: put it at a public URL. Secret scan first; static builds go to GitHub Pages at no cost (sign-up guide, device-code login, one question: it will be public); a server only when a backend is needed, cost asked once; then open the URL, rerun the acceptance on the live page, bind a domain if they want one.

    skills/ship/SKILL.md on GitHub (opens in a new tab)
  • verify

    S5 of see-it-ship-it: prove it works before saying so. Silent quality checks after every feature, a full review of every file before save and deploy, and the acceptance table (check / expected / actual / match) run on the local build and again on the live URL. Never 'tests passed'.

    skills/verify/SKILL.md on GitHub (opens in a new tab)

Review before you install

A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.