{
  "video_id": "reddit_1tzlq8w",
  "channel_slug": "ClaudeAI",
  "channel_handle": "r/ClaudeAI",
  "title": "Do I gatekeep these skills or share with wider team?",
  "url": "https://www.reddit.com/r/ClaudeAI/comments/1tzlq8w/do_i_gatekeep_these_skills_or_share_with_wider/",
  "external_url": null,
  "upload_date": "20260607",
  "published_at": "2026-06-07T19:35:26+00:00",
  "transcript": "Hi Clauders, \n\n  \nI recently wrote a skill on a whim at work. I'm based in the US, if that matters. I was frustrated at how many errors were slipping through in client deliverables as the content producers are too overworked to notice anything going wrong, while the reviewers just merely gloss over the deliverables and leave minimal feedback. \n\n  \nI asked came up with a skill in Microsoft Copilot Cowork using Claude's models. It can now very thorough check through each 500 page deliverable (in tranches), and leave details feedback. This is a very significant efficiency and quality gain. \n\n  \nHere comes the issue: I don't want senior management to be recklessly using it and become overambitious in assigning work to everyone under the guise of \"AI can speed it up a lot\" \n\nWhat would you do?\n\n\n\n--- Top Comments ---\n\n\n[1 upvotes] **TL;DR of the discussion generated automatically after 40 comments.**\n\nThe thread is pretty divided, but here's the breakdown of the two main camps.\n\nThe top-voted comments are telling you to **gatekeep that skill like it's the last slice of pizza.** The consensus here is that your unique skills are your job security. Sharing a tool that makes everyone more efficient could make you redundant, and you should never train your own replacement unless you're getting a fat promotion for it.\n\nHowever, a highly-upvoted counter-argument, described as the \"senior-level corporate\" take, says that gatekeeping is a short-sighted move. The real 4D chess play is to **share the skill, but own the entire rollout.** This positions you as the indispensable internal AI expert, which is far more valuable than being the secret wizard in the corner. To handle your concern about management, you need to create clear documentation on the tool's limitations (e.g., \"This checks for X, it does not replace Y\").\n\nA crucial caveat was added to the \"share\" strategy: **this only works if your company actually rewards innovation.** If your workplace is toxic and more likely to give you a plaque and then lay you off\n\n[124 upvotes] Keep them close as they are what prevent you being fired. I keep mine. \n\n[68 upvotes] Agree with most here . 1) what keeps you valuable keeps you hired . 2) never train your potential or actual replacement unless you are leaving in your terms. I have about 30 more of these fyi \n\n[51 upvotes] Share it, but own the rollout.\n\nGatekeeping buys you 3-6 months before someone else builds something similar. Sharing with you as the architect who runs the implementation makes you the internal AI expert for a process that touches senior leadership. That's the better position.\n\nThe management misuse concern is real but solvable: document exactly what it checks and what it can't catch. Make that part of the handoff. \"This flags formatting issues and logical gaps, it doesn't replace judgment on client-specific context\" -- that one sentence in a one-pager prevents 80% of the overreach.\n\nThe people who gatekeep usually end up watching someone else get credit for the same tool 6 months later.",
  "transcript_chars": 3044,
  "ingested_at": "2026-06-08T01:30:03.922244+00:00",
  "source": "reddit",
  "yt_meta": {
    "score": 52,
    "upvote_ratio": 0.81,
    "num_comments": 59,
    "author": "Natural-Round8762",
    "is_self": true
  }
}