Agent skill

Social Signal And Tact

by FAIRY123456789 in FAIRY123456789/human-edge-agent-skills

Read relationship signals across a conversation, infer what changed between turns, then turn awkward, overly formal, blunt, or AI-sounding messages to teachers, leaders, mentors, senior colleagues…

MITAuto-check passedWriting & Content

Install Social Signal And Tact

skills CLI
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill social-signal-and-tact -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FAIRY123456789/human-edge-agent-skills social-signal-and-tact --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/social-signal-and-tact .claude/skills/social-signal-and-tact && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
social-signal-and-tact
GitHub stars
103
Token cost
~3.8k tokens
SKILL.md length
2,089 words
Files
3 (incl. references)
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Read relationship signals across a conversation, infer what changed between turns, then turn awkward, overly formal, blunt, or AI-sounding messages to teachers, leaders, mentors, senior colleagues…

  • Works in 6 steps: Literal content — what was explicitly… → Relational move — praise, trust, role… → Evidence strength — whether the signal… → …
  • Upward communication
  • SKILL.md covers Core idea, Read signals before drafting, Chinese-native drafting rules and Relationship pacing rules, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Social Signal And Tact is an agent skill from FAIRY123456789/human-edge-agent-skills. Read relationship signals across a conversation, infer what changed between turns, then turn awkward, overly formal, blunt, or AI-sounding messages to teachers, leaders, mentors, senior colleagues, partners, acquaintances, or potential professional contacts into short, natural, relationship-aware communication. Use for tactful praise, upward communication, progress updates, favors, reminders, apologies, disagreement, gift and courtesy messages, proxy greetings, holiday wishes, warm friend-like chat…

Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `README.md` and `references/message-patterns.md`).

It sits in Writing & Content, covering Humanizing AI text. The repository describes itself as: 18 portable Agent Skills for voice-native AI, human judgment, microbets, social tact, writing, life systems, and safe deployment. The licence is MIT.

When your agent uses it

  • Upward communication
  • Progress updates
  • Gift and courtesy messages
  • Proxy greetings

Example prompts

  • “/social-signal-and-tact”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Literal content — what was explicitly said or requested.
  2. Relational move — praise, trust, role assignment, face-saving, invitation, disclosure, endorsement, obligation, testing, distancing, or a…
  3. Evidence strength — whether the signal is a single polite phrase, repeated across turns, public in front of third parties, costly in time…
  4. Role change — whether the user is being treated as a student, peer, trusted junior, collaborator, helper, family-adjacent guest, or…
  5. Response objective — receive the signal, protect status balance, deepen trust, keep optionality, make a practical next step, or…
  6. Overreach risk — what the user would be assuming if they responded too strongly.

What it can do on your machine

Read from SKILL.md and the folder at commit 31a0a16. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Social Signal And Tact loads about 3.8k tokens when it runs, and up to ~7.3k if it reads all its reference files. Until then it costs about 166 tokens; SKILL.md has 2,089 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~166
When it runs · the whole SKILL.md, loaded when a task matches
~3.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FAIRY123456789/human-edge-agent-skills at commit 31a0a16, republished under its MIT licence (© FAIRY123456789). 2,089 words, ~3,800 tokens.

Download SKILL.mdSave it as .claude/skills/social-signal-and-tact/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
social-signal-and-tact
description
Read relationship signals across a conversation, infer what changed between turns, then turn awkward, overly formal, blunt, or AI-sounding messages to teachers, leaders, mentors, senior colleagues, partners, acquaintances, or potential professional contacts into short, natural, relationship-aware communication. Use for tactful praise, upward communication, progress updates, favors, reminders, apologies, disagreement, gift and courtesy messages, proxy greetings, holiday wishes, warm friend-like chat, trust-building, private invitations, role entrustment, third-party endorsement, and deciding when not to convert goodwill into a request.
license
MIT
metadata.author
Joy T <101039451+FAIRY123456789@users.noreply.github.com>
metadata.tags
communication, tone, relationships

Social Signal and Tact

Read the relationship before writing the sentence.

Core idea

Good “人情世故” is the ability to understand what the other person cares about, protect both sides' face, make appreciation concrete, and let the real request or sentiment arrive with the right emotional temperature.

For chat, read the interaction as a sequence of turns, not only as one finished paragraph. Sometimes the most natural message is shorter because part of the context should wait until the other person responds.

The skill should solve two tasks in order: first determine what the other person's words changed in the relationship; then decide how much of that change to acknowledge in the next message. Do not draft before the signal reading is clear.

Read signals before drafting

For any conversation with meaningful relationship stakes, silently reconstruct the interaction using these fields:

  1. Literal content — what was explicitly said or requested.
  2. Relational move — praise, trust, role assignment, face-saving, invitation, disclosure, endorsement, obligation, testing, distancing, or a concrete offer.
  3. Evidence strength — whether the signal is a single polite phrase, repeated across turns, public in front of third parties, costly in time or reputation, or backed by a concrete action.
  4. Role change — whether the user is being treated as a student, peer, trusted junior, collaborator, helper, family-adjacent guest, or potential professional contact.
  5. Response objective — receive the signal, protect status balance, deepen trust, keep optionality, make a practical next step, or deliberately leave the resource question untouched.
  6. Overreach risk — what the user would be assuming if they responded too strongly.

Use cumulative evidence. Repeated specific praise is stronger than one compliment. Public advocacy in front of relevant third parties is stronger than private praise. An invitation into private or family space usually signals more relational warmth than a generic “有空联系”. A concrete introduction, meeting arrangement, document request, or work assignment is stronger evidence of resource intent than encouragement alone.

Do not collapse different signal types into one conclusion. Personal warmth can coexist with professional uncertainty. Praise can be sincere without implying a job, internship, introduction, or future commitment.

A useful internal scale is:

  • L0 — Courtesy: greetings, thanks, routine politeness.
  • L1 — Personal recognition: specific praise, remembered detail, voluntary encouragement.
  • L2 — Trust / role entrustment: asking the user to help, advise, accompany, represent, or look after someone; repeated or public endorsement also belongs here.
  • L3 — Private-circle opening: home-town invitation, family context, personal disclosure, reciprocal hospitality, or inclusion in a more private social setting.
  • L4 — Resource activation: a concrete introduction, invitation to a work setting, request for a résumé or proposal, named follow-up owner, scheduled meeting, actual task, or explicit offer.

Treat the scale as evidence discipline, not a rigid social ranking. The next message usually matches the observed level or stays slightly below it. Move higher only when the other person has opened that layer first or when a concrete reciprocal gesture is natural.

Chinese-native drafting rules

When the message is Chinese, draft from Chinese conversational logic rather than building an English outline and translating it sentence by sentence. This matters most in WeChat messages to teachers, mentors, leaders, founders, elders, and other senior people.

Prefer person → event → action → feeling over abstract concepts → grouped points → summary judgment. A Chinese message should usually move through what the person said, what happened, and what the user genuinely felt. Do not force several ideas into an English-style list and then close with a generic evaluation such as 这几个点给我很大启发.

Treat connective words such as 也 / 还 / 还是 / 又 as a review trigger when they function like automatic translations of also / too / still / again. Keep them only when they carry real meaning. Do not use them merely to manufacture progression, for example 今天又想了想,还是想专门跟您说声感谢 when a direct 非常感谢您昨晚愿意和我聊这么久 is more natural.

Do not manufacture reflection time. If the conversation happened the previous night, avoid phrases such as 今天静下来以后重新想了一遍, 到今天还一直记着, or other wording that makes one night's interval sound like long-term沉淀. Start from the actual interaction and gratitude unless the user explicitly describes a later reflection process.

Keep the speaker's causal order exact. If a senior's business advice was 先确定自己的预期 → 再看客户需求 → 以预期为尺度调整产品和定价 → 找到平衡, preserve that order. Do not rewrite it into a more familiar framework such as 先看客户需求,再结合自己的预期 merely because it sounds smoother.

Show humility through position and experience, not ceremonial self-deprecation. Natural forms include 您愿意跟我这样一个晚辈聊这么久 and 以我现在的经历,很多话可能还理解不到您真正想表达的深度. Avoid turning humility into a polished speech about how shallow, immature, or ignorant the user used to be unless the user genuinely wants to say that.

Use the user's own syntax as the first reference. Preserve natural repetition, emphasis, and slightly uneven human rhythm when it sounds like the user. Polish only enough to improve clarity, respect, and tact. Do not replace the user's Chinese with generic AI gratitude language.

One idea should normally appear once. If 想通 / 认知提升 / 运动让人静下来 express one connected insight, merge them into one compact passage instead of explaining the same realization across several paragraphs.

Relationship pacing rules

When a senior person gives the user a higher-status role over a peer, protect both relationships. For example, if a parent says “please help him become more disciplined,” do not accept a supervisory posture too literally. Reframe it as 互相督促 / 一起进步 / 能帮上的尽力 unless the user truly has formal responsibility. This receives the elder's trust while preserving the peer's dignity.

When praise becomes identity-level—such as maturity, judgment, execution, or future potential—receive it with modesty and one grounded sentence. Do not argue with the praise, amplify it into self-promotion, or immediately attach a request.

When the other person opens a private or family layer, deepen only with true specifics. A reciprocal invitation can be more natural when it names a real place, food, activity, or shared interest. Specificity turns a ceremonial “欢迎来玩” into a believable future social scene. Use this only when the warmth has already been opened by the other person.

Do not cash out goodwill too early. A compliment, public endorsement, or invitation can increase trust without yet becoming a professional resource. Preserve the relationship until there is an L4 trigger or a separate, naturally justified reason to ask. This is especially important when the same network may later contain internships, introductions, collaboration, or hiring opportunities.

When the other person's message reveals two identity anchors, respond to the one that matters most to them. A senior may care about professional expertise and family responsibility at the same time. A short, specific acknowledgement of both can show that the user actually listened. Avoid inventing emotional depth that the conversation did not support.

Show full SKILL.md (1,008 more words)Show less

Workflow

  1. Identify the relationship: teacher, leader, mentor, senior colleague, partner, acquaintance, potential professional contact, or real friend.
  2. Infer the immediate social goal: report progress, ask for help, praise, thank, remind, repair awkwardness, disagree, give a gift, pass on greetings, send a holiday wish, make a request, receive trust, or respond to a relationship upgrade.
  3. Reconstruct the signal sequence using literal content → relational move → evidence strength → role change → response objective → overreach risk. If the user asks what the other person “really means,” answer this before drafting.
  4. Check the speaking perspective, especially with teachers, mentors, senior people, or benefactors. Build from what the user saw, remembered, is doing now, or genuinely appreciates. Do not evaluate the other person's life, summarize their personality, infer their habits, or arrange their future. Even when the user supplies an observable detail, mention it neutrally from the user's perspective instead of converting it into a judgment about the recipient.
  5. Separate observable facts from interpretation. Praise should attach to something real: a decision, useful feedback, a result, a way of thinking, a resource, or a concrete effect on the user. In gratitude messages, one small true memory—an action, a sentence, or one concrete act of help—is usually enough.
  6. Estimate relational distance, signal level, evidence confidence, and channel. A WeChat message to a familiar teacher should not read like an official email. Do not infer L4 resource activation from L1–L3 warmth alone.
  7. Identify the other person's likely priority: progress, respect, control, efficiency, recognition, low-risk execution, being understood, family concern, trust, or receiving a gesture without social pressure.
  8. Decide whether the user should receive, mirror, slightly under-match, or defer the signal. For upward relationships, under-matching by a small amount is often safer than escalating faster than the other person.
  9. Choose one pattern from references/message-patterns.md. Use multiple techniques only when the message still feels natural. For teacher or mentor holiday gratitude, use the dedicated pattern there.
  10. Decide whether the content belongs in one send or several chat turns. Split WeChat messages by social function, not merely for visual formatting. If the situation contains both immediate logistics and relational explanation, lead with the immediate fact, then add the relationship context in a second message or after a natural reply. Avoid front-loading delivery details, apology, family context, product explanation, and well-wishes into one dense block.
  11. For gifts or courtesy visits, describe enough to make the gesture understandable, then stop. State the source, timing, local or seasonal quality, or caring intention when relevant. Do not sell the gift through price, brand prestige, rankings, exaggerated scarcity, or medical claims.
  12. Match the weight of the apology to the actual situation. For a minor absence or missed visit, phrases such as 有些过意不去 and 让我代他向您问好 are often proportionate. Reserve 请您见谅 or stronger apology language for situations that genuinely require repair.
  13. Make senior-facing closing language invitational rather than directive. Prefer 您回办公室后可以尝尝呀,希望您吃着喜欢 over commands such as 记得拿一下 when the context is a gift.
  14. Never frame a senior, mentor, or benefactor as someone who only came to mind because of the occasion. Avoid phrases such as 很久没联系了, 正好借教师节向您问个好, 顺便跟您问候一下, or 刚好想到您. Enter from the relationship itself: a direct blessing, gratitude, one real memory, or a current update.
  15. Keep each send short by default. In chat, one compact paragraph often works better than a structured memo, and two or three functionally distinct messages can work better than one overloaded paragraph.
  16. Remove AI markers: generic praise, repeated thanks, over-explaining background, emotional overstatement, bureaucratic transitions, three-stage mini-essays, English-style grouped abstractions such as A、B、C,这几个点给我很大启发, mechanical 也 / 还 / 还是 / 又 progression, and ornamental parallel endings such as 把 A,把 B or 做好 A,走稳 B. Stop once one natural meaning is complete; do not add a second action merely for rhythm.
  17. Make the other person easy to respond to. Requests should be clear and low-friction, with room for timing or refusal when appropriate.
  18. If professional optionality exists, check whether the current turn truly contains an L4 trigger. If it does not, do not force a résumé, internship, job, collaboration, or introduction request into a relationship-building exchange.
  19. Run the final check below.

Final check

  • What changed in the relationship during the last turn?
  • Is that change supported by words only, repeated behavior, public endorsement, costly action, or a concrete next step?
  • Am I treating warmth as a resource commitment without evidence?
  • Is the user being assigned a role over a peer that should be softened into mutual support?
  • Would a real person send this, and would they send all of it at once?
  • Does any sentence make the senior person feel evaluated by the user?
  • Does it contain an inference the user did not explicitly provide?
  • Could it make the recipient feel remembered only because a holiday arrived? In holiday greetings, remove phrases such as 很久没联系了, 正好借教师节问个好, or 顺便问候一下.
  • Did the draft add an unnecessary sentence for polish, symmetry, or a sense of completeness?
  • Does the Chinese read as if it was first organized in English and then translated? Remove grouped-concept summaries, unnecessary 也 / 还 / 还是 / 又, and artificial reflection-time phrases.
  • Does the draft preserve the speaker's original causal order, especially when restating advice, business logic, or decision rules?
  • Is one insight being explained twice under different words such as 想通, 认知, and 静下来?
  • Should this WeChat message be split into multiple bubbles with distinct social functions?
  • If the relationship just became warmer, does the response receive that warmth without immediately turning it into a favor or professional ask?

Tone controls

The user may ask for one of these:

  • 克制礼貌
  • 熟一点但不冒犯
  • 自然拍一下马屁
  • 汇报中顺手归功
  • 请教式
  • 轻松朋友感
  • 有分寸地反对
  • 送礼/代问候
  • 节日感谢
  • 潜在人脉关系维护
  • 关系信号拆解
  • 先养关系,暂不提资源

Friend-like naturalness is allowed when the wording fits the real relationship. Fabricated intimacy is not.

Integrity guardrail

Do not invent shared memories, private closeness, endorsements, affection, resource commitments, or facts. Do not coach deception that materially misrepresents the user's relationship or situation. For supplements, health products, or wellness gifts, avoid unsupported efficacy claims and status claims; keep the message focused on care and the actual gift.

© FAIRY123456789, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/social-signal-and-tact of FAIRY123456789/human-edge-agent-skills.

  • SKILL.md
  • README.md
  • references/message-patterns.md

Open the folder on GitHubat commit 31a0a16

Compare with similar skills

Social Signal And Tact next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Social Signal And Tact compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Social Signal And Tact this skillFAIRY123456789/human-edge-agent-skills103—~3.8kAutomated safety check: PassMIT
HumanizerAzure-Samples/interview-coach-agent-framework17338 repos~5.8kAutomated safety check: PassMIT
Avoid AI Writingconorbronsdon/avoid-ai-writing4.9k3 repos~8.1kAutomated safety check: PassMIT
User-Facing Text Cleanupguillaumemeyer/watermarks-remover24k—~3.5kAutomated safety check: PassMIT
Install Anti Sloptrycompai/crm11k1 repos~881Automated safety check: PassMIT
Stop SlopXe/site7328 repos~423Automated safety check: PassMIT

Similar skills

  • Humanizer

    Azure-Samples/interview-coach-agent-framework

    Official

    Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.

    173 GitHub starsUsed in 38 repos~5.8k tokens
    Writing & ContentAuto-check passed
  • Avoid AI Writing

    conorbronsdon/avoid-ai-writing

    Audit and rewrite content to remove AI writing patterns ("AI-isms").

    4.9k GitHub starsUsed in 3 repos~8.1k tokens
    Writing & ContentAuto-check passed
  • User-Facing Text Cleanup

    guillaumemeyer/watermarks-remover

    Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.

    24k GitHub stars~3.5k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Install Anti Slop

    trycompai/crm

    Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.

    11k GitHub starsUsed in 1 repo~881 tokens
    Writing & ContentAuto-check passed
  • Stop Slop

    Xe/site

    Remove AI writing patterns from prose. An agent skill from Xe/site.

    732 GitHub starsUsed in 8 repos~423 tokens
    Writing & ContentAuto-check passed
  • Chinese Text Humanizer

    op7418/Humanizer-zh

    Edits Chinese articles, comments and documents to remove filler, repetition and template phrasing while keeping the facts, the level of certainty and the author's voice.

    19k GitHub stars~2k tokensUpdated 18 days ago
    Writing & ContentAuto-check passed

More from FAIRY123456789/human-edge-agent-skills

All 18 skills in this repo
  • Aliyun Fullstack Deploy

    FAIRY123456789/human-edge-agent-skills

    Deploy full-stack apps to user-authorized Alibaba Cloud ECS or comparable Linux VPS hosts with preflight, canary verification, and rollback.

    103 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed
  • Skill From Scars

    FAIRY123456789/human-edge-agent-skills

    Mine repeated pain from transcripts, project retrospectives, debugging logs, failed prompts, deployment notes, or work history and decide whether it deserves to become a reusable Agent Skill.

    103 GitHub stars~856 tokensUpdated yesterday
    Auto-check passed
  • Voice Dump To Todo

    FAIRY123456789/human-edge-agent-skills

    Convert a long, messy, repetitive, speech-recognition-heavy task dump into a precise executable to-do list.

    103 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Deployment Proof

    FAIRY123456789/human-edge-agent-skills

    Convert deployment logs, validation reports, Git history, and comparison notes into a redacted GitHub case study, portfolio entry, interview story, and evidence-backed resume bullets.

    103 GitHub stars~980 tokensUpdated yesterday
    Auto-check passed
  • Vibe To Spec

    FAIRY123456789/human-edge-agent-skills

    Convert messy voice input, imperfect speech recognition, half-formed product ideas, and iterative corrections into an implementation-ready software specification for Codex, Claude Code, Copilot…

    103 GitHub stars~997 tokensUpdated yesterday
    Auto-check passed
  • Build In Public Launcher

    FAIRY123456789/human-edge-agent-skills

    Turn a finished or nearly finished Skill, plugin, repository, micro-tool, research utility, or AI project into a credible public launch that can earn real users and feedback.

    103 GitHub stars~708 tokensUpdated yesterday
    Auto-check passed

Questions about Social Signal And Tact

What does Social Signal And Tact do?

Read relationship signals across a conversation, infer what changed between turns, then turn awkward, overly formal, blunt, or AI-sounding messages to teachers, leaders, mentors, senior colleagues…. Social Signal And Tact is an agent skill from FAIRY123456789/human-edge-agent-skills. Read relationship signals across a conversation, infer what changed between turns, then turn awkward, overly formal, blunt, or AI-sounding messages to teachers, leaders, mentors, senior colleagues, partners, acquaintances, or potential professional contacts into short, natural, relationship-aware communication.

When should I use Social Signal And Tact?

Social Signal And Tact fits situations like: upward communication; progress updates; gift and courtesy messages; proxy greetings.

How do I install Social Signal And Tact in Claude Code?

Run `npx skills add FAIRY123456789/human-edge-agent-skills --skill social-signal-and-tact -a claude-code`. Or copy the skill folder (skills/social-signal-and-tact in FAIRY123456789/human-edge-agent-skills) into .claude/skills/social-signal-and-tact in your project. Claude Code loads it when a task matches its description.

How do I install Social Signal And Tact in Codex?

Run `npx skills add FAIRY123456789/human-edge-agent-skills --skill social-signal-and-tact -a codex`. Or copy the skill folder (skills/social-signal-and-tact in FAIRY123456789/human-edge-agent-skills) into .agents/skills/social-signal-and-tact in your project. Codex loads it when a task matches its description.

Can I use Social Signal And Tact in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FAIRY123456789/human-edge-agent-skills --skill social-signal-and-tact -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/social-signal-and-tact, .gemini/skills/social-signal-and-tact, .github/skills/social-signal-and-tact and .opencode/skills/social-signal-and-tact in your project.

What does Social Signal And Tact need to run?

SKILL.md names no scripts, command-line tools or credentials: Social Signal And Tact is instructions for the agent only.

Does Social Signal And Tact access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Social Signal And Tact safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Social Signal And Tact use?

Social Signal And Tact is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Social Signal And Tact use?

About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.5k tokens, read only when the agent opens those files.

What are the alternatives to Social Signal And Tact?

Skills that share tags, products or a category with Social Signal And Tact: Humanizer (Azure-Samples/interview-coach-agent-framework, 173 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), User-Facing Text Cleanup (guillaumemeyer/watermarks-remover, 24k stars) and Install Anti Slop (trycompai/crm, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Social Signal And Tact?

FAIRY123456789 (a GitHub user) maintains it in FAIRY123456789/human-edge-agent-skills, which has 103 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 10, 2026.

Source: FAIRY123456789/human-edge-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.