agentleFS
Sign inStart free
CodesbyFebinCodesbyFebin/linkedin-manager/docs/llms.txt

linkedin-manager

llms.txt0 starsChanged 39 days agoMITView on GitHub

Version: 1.4.3 License: MIT Maintainer: Febin Francis (CodesbyFebin)

The file

We split this llms.txt into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No API key is needed for drafting.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 3,592 llms.txt files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
llms.txt
# LinkedIn Manager
> 40 agent skills for LinkedIn, X, Instagram, YouTube, and WhatsApp. Draft, audit, approve. Optional APIs; publishing requires approval.

Version: 1.4.3
License: MIT
Maintainer: Febin Francis (CodesbyFebin)

## Documentation
- [Repository](https://github.com/CodesbyFebin/linkedin-manager): Installation, supported APIs, approval workflow, and limitations.
- [Skill index](https://github.com/CodesbyFebin/linkedin-manager/blob/main/SKILLS.md): All 40 skills with full descriptions and source links.
- [JSON catalog](https://codesbyfebin.github.io/linkedin-manager/skills.json): Names, paths, descriptions, version, and source URLs.
- [Root workflow](https://github.com/CodesbyFebin/linkedin-manager/blob/main/SKILL.md): Routing and shared rules.
- [Security](https://github.com/CodesbyFebin/linkedin-manager/blob/main/SECURITY.md): Credential handling and reporting.

## Boundaries
No API key is needed for drafting. Optional Apify reads, Publora writes, and Pixfaro images require separate service accounts and may be billed.
The scheduling CLI prompts for approval unless --approved attests prior approval of the exact action. Low-level library callers must enforce approval themselves.
Other platform desks and job application skills produce drafts, not automated sends or applications.
Metadata does not guarantee indexing, answer-engine citations, engagement, stars, or forks.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free