Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Remote Work Guide

ASecurity

Thrive in remote roles with async communication habits, home-office setup, and visibility strategies.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgo

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill remote-work-guide --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Remote Work Guide?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Remote Work Guide
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-remote-work-guide/badge)](https://www.skillsdirectory.com/skills/aicodedecode-remote-work-guide)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: remote-work-guide
description: Thrive in remote roles with async communication habits, home-office setup, and visibility strategies.
category: career
---

## Overview

Remote work removes the office's ambient structure — the hallway chats, the
visible busyness, the
easy questions — and replaces it with nothing unless you build deliberately.
High-performing remote
workers master three things: written communication, proactive visibility, and
boundaries. This skill
covers all three plus the practical setup.

## When to use

- Starting a first remote role or transitioning from office work

- Improving async communication and meeting effectiveness

- Setting up a productive home office

- Staying visible and promotable while remote

- Managing energy, isolation, or burnout in remote work

## Core concepts

- - - **Default to async, written, public.** Decisions in docs and threads, not
  DMs and calls. Written
  records are searchable, timezone-proof, and force clearer thinking. If it
matters, write it where
  the team can find it.
- - - **Over-communicate intent and status.** In an office, presence signals
  work. Remote, you must
  narrate: what you're working on, what you're blocked on, when you'll be
offline. A 2-line daily
  update prevents 10 "just checking in" messages.
- - - **Visibility is a system.** Remote promotions go to people whose impact is
  legible: written
  updates, demos, docs, helping visibly in public channels. Do good work where
people can see it.
- - - **Meetings earn their slot.** Every recurring meeting should justify
  itself quarterly. Default
  25 minutes, agenda in the invite, notes with owners and dates. Camera on for
small discussions;
  camera optional is fine for large broadcasts.
- - - **Boundaries are infrastructure.** Set hours, communicate them, and
  actually log off. The laptop
  on the kitchen table will consume evenings unless a shutdown ritual defends
them.
- - - **Timezones are a design constraint.** Overlap hours are precious —
  protect them for
  collaboration, push everything else async. Rotate painful meeting times; don't
let one region
  always suffer.

## Practical workflow

1. 1. 1. **Set up the workspace.** Dedicated desk if possible, external monitor,
   decent chair, good
   lighting, reliable internet with a backup (phone hotspot). Noise-canceling
headphones are the
   highest-ROI purchase.
2. 2. 2. **Establish the operating rhythm.** Fixed start/end times, a morning
   planning block, calendar
   blocks for deep work, and a shutdown ritual (review tomorrow, close the
laptop, change context).
3. 3. 3. **Build the communication stack.** Learn your team's norms: what goes
   in chat vs email vs docs
   vs calls. Then exceed them slightly — faster responses during overlap hours,
clearer status
   updates, better meeting notes.
4. 4. 4. **Create visibility loops.** Weekly written update to your manager
   (wins, priorities,
   blockers). Monthly: share something useful with the broader team — a doc, a
demo, a lesson
   learned.
5. 5. 5. **Engineer connection.** Schedule virtual coffees, join or start
   interest channels, attend
   offsites fully present. Relationships need deliberate investment without
hallway serendipity.
6. 6. 6. **Manage energy.** Movement breaks, real lunch away from the desk,
   sunlight. Isolation creeps
   up — coworking days, walking meetings, or local communities counter it.
7. 7. 7. **Quarterly self-audit.** Am I visible? Is my communication clear? Are
   boundaries holding? Ask
   your manager directly: "what would make my remote effectiveness obvious to
you?"

## Common pitfalls

- - - **Invisible excellence.** Doing great work nobody hears about. Remote
  rewards narrators, not
  just builders — document and share.
- - - **Meeting overload.** Saying yes to every invite fragments the day. Audit
  ruthlessly; decline
  with a written update instead.
- - - **Always-on availability.** Instant replies at all hours train people to
  expect them.
  Response-time norms beat constant presence.
- - - **Camera-off disengagement.** In small meetings, camera off reads as
  absent. Default on for
  discussions under ~8 people.
- - - **Letting isolation compound.** Skipping social touchpoints "to focus" for
  months leads to
  disconnection and, eventually, disengagement. Connection is maintenance, not
luxury.
- - - **No separation between work and home.** Working from the couch, in
  pajamas, with no end time.
  Environment cues matter — build them deliberately even in a small space.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →