Skill: 21f2000735/modern-chanakya (version 1.0.3)

--- name: modern-chanakya description: Interpret Chanakya, Chanakya Niti, Arthashastra, and reliable historical/wiki-style summaries into modern practical guidance for systems, software, product building, career strategy, discipline, leadership, governance, and execution. Use when the user wants Chanakya-style principles, modern applications of classical ideas, or a growing indexed knowledge system of Chanakya thought adapted to present-day work and life. --- # Modern Chanakya Use this skill to transform classical Chanakya ideas into modern, grounded, reusable guidance. ## Core purpose This skill should not merely repeat ancient wording. It should: - identify the principle behind the verse, story, or strategic idea - separate source-backed meaning from modern interpretation - translate it into present-day software, systems, product, career, and life contexts - keep the insight memorable, practical, and reusable - build a growing knowledge system over time ## Source discipline Use these source layers carefully and in order of trust: 1. direct classical references when available 2. reliable scholarly summaries 3. historically grounded reference material 4. high-quality encyclopedic/wiki summaries for orientation 5. modern commentary only when clearly marked as interpretation Do not present internet folklore as certain Chanakya truth. Always distinguish: - original idea - historical meaning - modern interpretation - confidence level of the explanation Use confidence labels in practice: - **high** → strongly source-backed - **medium** → reasonable interpretation with decent grounding - **low** → loose commentary, folklore, or uncertain attribution ## Core features ### 1. Principle extraction For each verse, story, or Chanakya-style idea: - identify the strategic principle - state it clearly in plain language - explain why it matters ### 2. Modern translation Translate the principle into modern domains such as: - software architecture - product design - career strategy - learning systems - execution discipline - leadership - governance and incentives - role clarity and organizational design ### 3. Example-first explanation Prefer small relatable examples over abstract grandness. Use examples from: - frontend/backend ownership - queue discipline - project structure - job switching - hiring/profile positioning - infrastructure and system design ### 4. Knowledge system building Maintain a structured collection of Chanakya-derived principles with: - title - source type - source note - original idea - historical meaning - modern interpretation - example - tags - related ideas - confidence ### 5. One-line current-work reflection When the user is actively building or solving something, allow short Chanakya-style one-liners tied to the current work. Use this sparingly. The line should be: - brief - relevant to the active task - clarifying, not ornamental Example shape: - `Chanakya note: a kingdom fails when the wrong layer owns the wrong responsibility.` ## Output patterns ### Short pattern - principle - modern meaning - one example ### Expanded pattern - original idea or paraphrase - historical meaning - modern interpretation - software/work/life analogy - practical action ## Style rules - keep the Chanakya touch sharp, strategic, and grounded - prefer clarity over theatrical language - keep insights memorable and compact - avoid decorative pseudo-wisdom - when uncertain, explicitly mark the wording as interpretive - minimal emoji are allowed in user-facing chat if they add a light human touch, but keep them sparse and secondary to the idea ## Knowledge discipline When gathering Chanakya knowledge: - avoid duplication - merge similar principles - tag by theme - keep retrieval easy - separate high-confidence source-backed ideas from looser commentary Suggested themes: - discipline - governance - incentives - structure - secrecy / information control - placement / right role - timing - alliances - risk - resource management - execution - learning ## When not to use Do not use this skill when: - the user wants plain direct execution with no philosophical framing - a simple factual answer is enough without Chanakya context - the source is too weak to support even a medium-confidence interpretation - Chanakya flavor would distract from clarity rather than help it ## Anti-patterns to avoid - fake certainty about weakly sourced lines - empty motivational quotes without practical use - vague spiritualization of strategic material - treating Chanakya as a meme instead of a systems thinker - collecting wisdom without indexing or reusing it - adding Chanakya flavor when plain directness would help more ## Working rule This skill should improve judgment and framing, not replace execution. Use it to sharpen thought, clarify structure, and deepen meaning — not to flood ordinary work with quotes. ## Reference Use `references/knowledge-format.md` for how to structure, store, and grow the Chanakya knowledge base.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)